Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.databases > #416
| From | "Alessio Stalla" <alessio.stalla@THRWHITE.remove-dii-this> |
|---|---|
| Subject | Re: Looking For Direction |
| Message-ID | <bc87a8ea-8ff9-474e-a568-e48501234cff@d37g2000yqm.googlegroups.com> (permalink) |
| Newsgroups | comp.lang.java.databases |
| References | <d4GdnQ9ebOqDa5LRnZ2dnUVZ_o-dnZ2d@earthlink. |
| Date | 2011-04-27 15:23 +0000 |
| Organization | TDS.net |
To: alt.comp.lang.java,comp.l On Jun 9, 11:19=A0pm, "JC" <jjcarde...@hotmail.com> wrote: > For the user interface I am thinking of something that is > integrated with a web browser. In addition to what everyone else said, I'd like to concentrate on this point. Are you really sure you need a web-based interface (i.e., do you really need to expose your application to potentially anyone anywhere), or are you considering it just because it's today's trend to build web applications? In my experience (2+ years in JSF + some minor projects with Struts) web applications often face an additional layer of complexity than client-server applications, and are generally limited in functionality (by the browser and by the stateless nature of the HTTP protocol). I think JSF especially is a very bad choice. I used the ICEFaces implementation, which adds its own host of problems, but JSF in general is terribly complex, and has a fundamentally bad design. Imagine someone proposed to you, for a client-server application: "hey, let's do this cool thing, let's keep *all* the GUI state on the server and ask for it *each and every time* the user interacts with the GUI"... you would say that's crazy, wouldn't you? Yet it's precisely what JSF does (and ICEFaces exacerbates the problem by forcing everything to be AJAX, even stuff that could be client-side only, like help tooltips). Then, there's the complex and strict life cycle, the macroscopic mistakes in the class hierarchy, and I could go on and on... So, I'd suggest you to use Swing + Java Web Start (JNLP) + Spring HTTP remoting to communicate with the server. If you really, really *need* a browser, consider GWT. It makes you write a JavaScript GUI... without JavaScript, using Java. Not as powerful as a client-server app, but relatively close. hth, Alessio --- * Synchronet * The Whitehouse BBS --- whitehouse.hulds.com --- check it out free usenet! --- Synchronet 3.15a-Win32 NewsLink 1.92 Time Warp of the Future BBS - telnet://time.synchro.net:24
Back to comp.lang.java.databases | Previous | Next | Find similar
Re: Looking For Direction "Alessio Stalla" <alessio.stalla@THRWHITE.remove-dii-this> - 2011-04-27 15:23 +0000
csiph-web