At the end of the day, its just JavaScript, which means you get the same communication that you would with JavaScript (i.e. XHR).
There are lots of ways to implement it though. Even though the transport mechanism is the same you could use GWT-RPC, RequestFactory, RequestBuilder, or JSONP. If your server is Java, look at GWT-RPC and RequestFactory first. GWT-RPC is good for general purpose services, but in a lot of cases RequestFactory makes it easier to work with server-side entities. Rob On Thu, Jul 7, 2011 at 7:09 PM, Gautam Kowshik <[email protected]>wrote: > I'm a GWT noob and have been trusted with the task of building a full > fledged game portal :-) Now iv been trying to organize the > componenents of the project into modules before i start full fledged > code development. My plan, for now, is to maintain each game as a > separate GWT module and interface with them over some communication > mechanism from a central portal main EntryPoint module. Now each game > might have it's own client (UI) and server services. I need the portal > to communicate with both client and server sides of each game. > Is this straightforward to do in GWT? Is it possible to import the > module's services into the portal's and have them communicate? > > -- > 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. > > -- 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.
