On Nov 5, 2010, at 1:42 PM, [email protected] wrote: > And this is precisely the point that I was trying to make. A browser is not > (currently) a suitable environment for writing desktop applications. But the > problem is not HTML. HTML is markup, and is perfectly fine for what I need to > do. > > The problem is that if I use a browser for writing desktop applications, then > I have to jump through a lot of hoops just to get basic stuff like this > working, just to prevent a user from doing something silly. > > You said that 'This is not how a web page is supposed to work'. I agree > completely. But this thread is about desktop applications. Not web pages. Two > different things. > > Speaking from personal experience, the clients we talk to are interested in > having web/browser based applications because: > > 1) It makes their deployment a lot easier. All they have to deploy is a > server. To update their applications, they deploy a new war. That's it.
You could have just as simple a deployment situation with a client-server Swing app, deployed via JNLP. You deploy your app to a single HTTP server, and that's it. In the simplest case of "pure" client-server, all your business logic is in the client, and your back end is a "dumb" database. You can still use ORM tools like Hibernate to simplify data access. A 3-tiered model introduces a bit more complexity, but it's not too hard to manage. Your client and server code are now separate, so you have a War and a JNLP bundle to deploy. But the backend can continue to use Hibernate, and the front end can call RESTful web services on the application server, and leave all the business rules on the server. Rob -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
