ePatha Software, LLC



Developer of Java™ based:

    web applications using JSP, SSL & Tomcat

    down-loadable Java™ Swing applications

    independent client-server applications

    integrated client-web applications

While the expression, "there is more than one way to skin a cat" is true, it is both horrific and disgusting. So let's instead say there are various methods to implement a computer application. At ePatha software we have used them all, because each has benefits and restrictions. Below these methods are discussed and illustrated.

web applications

pros

Since every computer user has access to a web browser of some kind, a web application gives your application basic access to every user and changes to your served pages are all centrally implemented.

cons

You must incorporate other functionality like Javascript (examples), Flash™ or Java Server Pages (JSP) to create dynamic presentations or obtain useful user input. In addition, there are often browser inconsistencies which may require conditional use statements.
Also, data transmissions between the user's browser and your server are readable by others, unless the data is encrypted by a Secure Socket Layer (SSL), which requires additional server administration.

example

In this application segment, created for GoCampaigns Inc., the user has access to customer information via SSL after a password protected login. Here the customer's data can be altered, deleted, or added to and all communication with the server process is encrypted.

The application is built using JSP's which communicate with a server based programs run via Tomcat (an open source tool to process JSP interaction).


down-loadable applications

pros

Since all user data hosting is local it is extremely secure and it does not require internet access. It is also operationally faster and capable of more intricate window decorations and interactions.

cons

It must be downloaded and installed on the user's computer.
Separate versions may be required for different operating systems.
Updates are not automatically propagated as they are with browser based applications.

example

This application (ePatha License Manager) is built using 100% Java™ Swing and requires no other facilities.


client-server applications

pros

User data can be hosted either locally or on your server via the internet. The user interface is not dependent on a browser or its plug-ins, so more intricate window decorations and interactions are possible.

cons

It must be downloaded and installed on the user's computer.
Separate versions may be required for different operating systems.
Updates are not automatically propagated as they are with browser based applications.
Also data transferred over the internet is not encrypted by default, so, if used, it must be done independently.

example

This application (part of LeadMiner™) is built using 100% Java Swing and Java server facilities. All the information in this window was transferred from the server dynamically, on-demand.


integrated client-web applications

pros

This application method has the best of both web and client-server features, because it employs whichever methods works best, as required.

cons

Since both web and client-server methods are being used, it also has the worst of both worlds.

example

This application (also part of LeadMiner™) is built using 100% Java™ Swing and Java™ server facilities. Here the information was sent via the client-server method and then, at the appropriate time, the client told the web browser to start an SSL session where the user could pay for the service. Then, when the service was paid for, the server would tell the client that the data could now be accessed.





updated March 17, 2010        contact       principal       License Manager™       Javascript gadgets