it is not necessary to have different protocols (RPC / whatever your J2ME uses) use the same servlet ... if the actual messaging work is done in a class outside the servlet, both your RPC servlet and J2ME endpoint can use the same underlying code and just handle the protocol stuff themselves. Still uses the same server, and is much less "hackish" than making the RemoteServiceServlet try to do something that it shouldn't be.
-jason On Apr 22, 2009, at 11:32 PM, mike wade wrote: > > Hi, > I am developing an instant messenger application that make use of GWT > RPC for client to server communication. The application works fine for > clients with full blown browsers like (ie, chrome etc..) In addition > to messaging between browser clients, the application must allow > communication between browsers users and J2ME based wireless phones. > > My problem is how do I get a J2ME device to communicate with the > server that was created for GWT. I need a single server because a J2ME > user and a browser user will exchange message through the common > server. My server is built around the gwt RemoteServiceServlet class. > > Is it possible to use the same server that was created for browser > clients for J2ME devices as well. If not, is there a different way to > unify the two platforms through a common server or container in real > time. > > I need the J2ME devices to share the same variables on the server and > have access to the same server methods as the browser users. > > Any help will be appreciated. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
