This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
hi,all my friends here, recently i have a project relavant to client / server base in distributed environment, my question is , what are the technology i need to include to this project ? i'm new in distributed system, but i do have some experience on java , what are the books recommended to read out in order to accomplish my project, thank you very much for helping !
the most basic technology for creating distributed apps is RMI (Remote Method Invocation). To learn more about RMI, check out William Grosso's book (Java RMI), which provides a really good introduction into RMI.
But you should also check out whether browser-based JSP/servlet solutions could do in your case.
thank you for your information , mag and catalin .
my application is actually develop accounting software which using server as host and other client which link to server database, so that during transcation in client, and server database be able to update database in synchronize way,
and we plan to make this as desktop application, so any suggestion on these ? desktop application make sense on this situation or web based ? thank you !
Joined: May 26, 2004
You can go with 2 tier architecture that includes a - Swing client that connects to the - Database Server
or a 3 tier architecture comprised of - Database Server - Web application comprised of servlets and JSPs hosted on a webserver (ex Tomcat). The web application will query the database - Browser that becames your GUI
Start designing the database, it will be the same for both architectures. Then develop the Swing client and then the web application. You should have them both if possible.
Joined: Jan 08, 2004
catalin, from your point , which model is faster ?
I suspect that the database operations will always dominate the response time, no matter which interface you choose. For a desktop application, the Java WebStart approach is much more flexible than a web based (browser/servlet or J2EE) approach. Bill