Yep, all the GET information is in the URL. So something on the order of "please send me 'X'" will work (response can, after all, be any size), but "here, have these 10 objects" is likely to choke.
I suppose you can override HttpServlet's service call. But, given a choice, I'm going to override GET. Greg On Nov 17, 10:27 am, ep <[email protected]> wrote: > by the way, why I dont recommend to use GET is because this http > method simply does not define to have body where you can put big > amount of data, its all about the url and its params and some extra > data like a header...no place for big payload > > On 17 Nov., 17:01, Greg Dougherty <[email protected]> wrote: > > > AbstractRemoteServiceServlet (which all GWT Servlets inherit from) > > declares "public final void doPost". So regardless of what you SHOULD > > do, if you've got a GWT Servlet that you want to ALSO handle HTTP > > requests, then is HAS to do it through doGet. > > > Unless you can point me to some hook in the processing chain I've > > missed? > > > Greg > > > On Nov 17, 8:53 am, ep <[email protected]> wrote: > > > > not sure if this will work outofthe box, since in GWT RPC there is > > > always a client which is initiating an RPC request first. so you have > > > to do so in your server code, except for there is nor XHR on the > > > server, the rest should work fine, especially serialization of the > > > request command, which you would pass from one servlet to another > > > using POST (not GET). > > > > do you have to use HTTP beyond or would be be ok to use just tcp or > > > udp socket? I'd either go for RMI, binary serialization (no http) or > > > JSONP / XML (http) which you can easily get started with, of course > > > SOAPis the king^^ but I guess would be kinda overkill here. > > > > On 17 Nov., 14:55, Greg Dougherty <[email protected]> wrote: > > > > > Use Java Serialization to send the the objects from one servlet to > > > > another. > > > > > Make sure you have the Objects implement Serializable. :-) > > > > > You can override doGet without damaging GWT RPC. One servlet does > > > > that, the other (the one driving the exchange) makes an HTTP call to > > > > it. They both use Object*Streams to send and receive the object(s). > > > > > Greg > > > > > On Nov 17, 6:52 am, Ice13ill <[email protected]> wrote: > > > > > > Hello, I want to send objects between 2 servlets and i was wondering > > > > > if the GWT RPC mechanism used for client - server communication can > > > > > also be used to send data across two servlets that extend > > > > > RemoteServiceServlet. > > > > > > Or maybe I can use the Java serialization to actually send bytes from > > > > > one servlet to another ? > > > > > > Any ideas ? -- 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.
