Re: Development mode cross site RPC requests
Hmmm, I glanced over that thinking it wouldn't allow me to do the convenient browser-refresh to test my client-side code... I should really look into it further. Thanks for the smack to the head ;-) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Development mode cross site RPC requests
My thinking exactly. Definitely worth investigating. Thanks for your suggestions! - Lars -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Development mode cross site RPC requests
Y'know I thought about that... In fact I thought about even using such a setup in prod mode. That way i could take advantage of the optimized across-the-wire serialized data transfers built in to GWT and save the client from downloading all the XML parsing logic. That would be done in this server side component. If I ever have time I'd like to explore that to see if there is a performance hit for this extra step or if the optimized transfers would make it a overall benefit. Thanks. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Development mode cross site RPC requests
Did you try this? http://code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebugging.html#How_do_I_use_my_own_server_in_development_mode_instead_of_GWT's -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Development mode cross site RPC requests
You could create a server side component for your GWT app, and delegate fetching the XML data to that. -Ben -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Development mode cross site RPC requests
I would think that the servlet would increase the performance of the application by a bit. XML parsing in JS can't be fun, or fast, for that matter. This assumes the latency between wherever you would run your application server and the target C++ backend isn't too high, though. Otherwise you are making a big triangle of a route, as opposed to simply back and forth. Probably still worth it, since then you can leverage awesome java XML parsing libraries. You may see some performance penalty for switching servers, I suppose. I seem to recall that Tomcat wasn't quite as zippy as Apache. -Ben -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
