I'm also quite newish, but I found the GWT-RPC very good. If your backend is written in Java, then this makes sense since you can work with the same POJO's on the back and front end.
If your backend is written in a different language or need more than one client to consure data, and GWT is just one of them, then you could use JSON and marshal the objects into client specific POJO's. I've done this before, but I found it less elegant than the RPC route On Wed, Jan 2, 2013 at 2:00 PM, <[email protected]> wrote: > I am new to GWT... And planning to develop a prototype in GWT for a > company... > Can anyone tell me how to decide on which clientserver communication is > suitable for my project.... > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-web-toolkit/-/N7j8bG6L8yQJ. > 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.
