websphere - Web-based clients vs thick/rich clients? -
my company software solutions provider major telecommunications company. environment ibm websphere-based front-end ibm portal servers talking cluster of back-end websphere application servers providing ejb services. of portlets use our own home-grown mvc-pattern , written in jsf.
recently did proof-of-concept rich/thick-client application communicates directly ejb's on back-end servers. written using netbeans platform , uses websphere application client library establish communication ejb's.
the painful bit, getting client use secure jaas/ssl communications. but, after resolved, we've found rich client has number of advantages on web-based portal client applications we've become accustomed to:
- enormous performance advantage (corba vs. http, cut out portal server middle man)
- development simplified , faster due use of netbeans' visual designer , swing's robust architecture
- the debug cycle shortened not having deploy client application test server
- no mishmash of technologies web-based development (struts, jsf, jquery, html, jstl etc., etc.)
after enduring pain of web-based development (even jsf) while now, i've come following conclusion: rich clients aren't right every situation, when you're developing in-house intranet-based solution, you'd crazy not consider netbeans platform or eclipse rcp.
any comments/experiences rich clients vs. web clients?
one benefit lot of calculations/validations can done on client side, allows each client share in processing load of overall application.
another benefit of thick client hold state in client. makes servers stateless , can scale lot better making fault tolerance breeze.
in our case have interfaces hardware in our app, scanners on serial ports workstations, have implemented jni layer printers can have application control of print jobs our application. (invoice printing)
for startup , distribution of new software have update jar run checks file on local system against deployed date on server see if local system date. if system out of date download jar files needed , launch app. avoids users needing go web page.
i recommend this book server side patterns relate new java ee stuff.
Comments
Post a Comment