Thanks Sri, Mike! Yes, it seems that a more transparent & light-weight protocol would be better in the long term.
MG On May 28, 12:10 pm, "[email protected]" <[email protected]> wrote: > Another, more recommended method is to isolate the business process > away from the GWT RPC. So you have a stand alone "middle-tier" that > you communicate with via GWT-RPC and Swing Clients and whatever else > you want to do. Don't try to reuse GWT-RPC....go around it. It's a > better design... > > On May 28, 9:40 am, Sripathi Krishnan <[email protected]> > wrote: > > > Having said that, I wouldn't build a production app that relies on the > > library. > > > If you really want to develop your services for multiple clients, I'd > > recommend staying away from GWT RPC. JSON is well suited for the browser, > > while XML is better suited for a Swing application. If you build your > > services to support both with the same codebase, you can reuse your services > > from a wide range of clients (Mobile apps / Swing / GWT etc) > > > --Sri > -- 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.
