Hi, I'm new to GWT, and I'm currently trying to architect what we hope
will be a webscale application. GWT seems to meet our requirements for
developing the browser application, but seems to be weak in it's
interaction and data binding with back end services other than a GWT
Java Servlets.
Since we have ruled any form of server side java out of our designs
(for obvious webscaling reasons). This seems to leave us with the
following choices for back end (stateless) services:
a) Traditional web services.
Pro's: c++ based (fast), interacts with Oracle Database
well, scales well, takes advantage of advanced oracle
features such as client side result cache. Will be
consistent with back end web services we need to
provide as client API's.
Con's: Looks like a lot of hand crafting is needed in GWT to
interact with traditional services, parse them, bind
them to widgets etc.
b) c++ Servlet container.
Pro's: Same as above
Con's: Not 100% it can be done with GWT, not sure if there
is a good free web scalable c++ servlet
container out there.
I'd be very interested in peoples opinions on whether i've grasped all
the GWT options, understood the effort required to bind with non gwt
services correctly, or indeed anyone with any experience of getting
GWT to interact with non GWT services, is it as painfull as it looks?
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" 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/google-web-toolkit?hl=en.
