I have created a Help Desk application for my department where I work. Originially it was an applet. Then I made it into a Desktop app to lose the sandbox. Then, I decided to make it into a Web App to make updates easier on me. Over the course of the different development stages I think I have gotten a pretty good grasp of how a good Help Desk application ought to work. And now I want to take that knowledge and build a really nice Open Source App. The question is now: 1. Create a Swing Desktop App 2. Create a Web Application (JSP/Servlets, probably STRUTS) If anyone could just voice their opinion as to which one and why they would prefer it that way, that would be great. Thanks.
i prefer web-apps because they don't require installation of anything client side (except a decent mozilla browser ) and so version control and patching isn't an issue and web app interfaces tend to be easier and more usable to everyone!
Kim Jong II (North Korea's Dear Leader) said:Nuclear weapons don't kill people, people kill people.
I kind of like the Web application version better, because the help desk can be accessible by anyone who has an internet browser, for the most part. The standalone application you have to worry about the different variables of the installation of the application, on each persons PC i.e. what operating sysytem, the correct version of java, etc. Just one of many opinions, I am sure. Craig.
I wonder if I had asked this in the SWING forum if I would be getting different opinions. I agree with all of the above statements. But I'm still not conviced either way. But since all so far are votes for Web Apps, I will play your advocate. We can all agree that Web App UI's are somewhat limited. And that a SWING app could be have many more features than a typical Web App. As far as updates are concerned, with the exception of minor patches, how often do your companies upgrade their applications to the newest versions, Web App or Desktop App? If they are anything like the company I work for, it's not very often if ever. If it aint broke.... Please keep the opinions comming though. I appreciate them.
Actually, if designed modularly enough, it could probably be done BOTH as a web app and a client/server app. I'm currently rolling my own web app framework (for the heck of it) that can (theoretically) be accessed from web pages or from a swing app and provide the same abilities. I'm only half done implementing the web app portion of it, so we'll see how well it's designed whenever I get around to developing the swing app for it
Gregg I would also vote for web app, assuming you do not need a really rich user interface. Another reason I tend to prefer these, all other things being equal, is that it allows me to pool database connections in one place and have a bit more control over where and when the db gets accessed from. Where I work we have some VB & Java fat client apps on desktops holding open lots of database connections unnecessarily. We have also found, as other people have already mentioned, that rolling out new releases and patches is a bit of a pain for the fat clients. Releasing to 160 desktops as opposed to one web server is definitely slower, more difficult, and more error prone, even if it only happens a couple of times a year. Michael
"One good thing about music - when it hits, you feel no pain" <P>Bob Marley
Hi, I feel web application is easy to made compared with applet/swings. Even all the J2ee people will suggest the same. All web application servers are changing from swing format to web application format I am not sure about the performance, but i observed that in Websphere application server 3.5(WAS3.5 is swing based),deploying a ejb took more time compared with current WAS 4.0(web application). Regards, M.S.Raman.