Hi Jan: I am with you on the separation of concern between GWT client and server using JSONP. Have you look at http://google-web- toolkit.googlecode.com/svn/javadoc/2.0/index.html in GWT trunk and work out a solution with a REST framework such as Restlet. Please share your experience.
Duong BaTien DBGROUPS and BudhNet On Sun, 2010-01-03 at 12:32 +0100, Jan Ehrhardt wrote: > Lucas, I don't agree with you. > > > I would recommend to use HTTP, since you can use JSON instead of XML > and JSON objects are directly available to your GWT app (JavaScript > overlays). > > > Furthermore in a RIA architecture (that's what GWT is developed for) > you should have clear separation between your client (GWT app inside > the Browser) and your server. this means, that your server should > provide a well defined flexible and easy to use service interface, to > call for data (includes writing of data). Such an interface can be > done best by using a RESTful architecture. So you'll get two benefits, > your GWT client can call the interface using JSON as exchange format > and other clients can do the same with XML, if they prefer. Most > frameworks support JSON and XML for REST out of the box, so you can > just place a format property in the HTTP request. > > > Another point is, that RPC makes it much easier to mix client and > server code. This means, that your separation of what belongs to the > client and what belongs to the server won't be as clear and > independent of each other. > REST instead will decouple both very well. So your client depends on a > RESTful interface but not on server side technology. You can even > switch the server to a complete new .NET implementation as long as it > provides the same RESTful API. > > > Regards > Jan Ehrhardt > > On Sun, Jan 3, 2010 at 12:12 PM, Lucas Vargas Freitas Ventura > <lucasvfvent...@gmail.com> wrote: > Sorry Pion, you are correct. Http supports syn and asyn calls. > > > When you are using Http, you receive from the server or Xml > file or a String (Key:value). It work fine for simple > applications. > > > But when you are building large and complex applications, you > follow some design patterns (MVC for example) to help you. I > think that using RPC is better in this case, you don't need to > worry about the Http state, don't need to "convert" your Xml > response, you just receive the java object that you create in > the server, all information that you need with easy access. > > > (sorry for the bad english) > > > On Sat, Jan 2, 2010 at 11:56 PM, Yozons Support on Gmail > <yoz...@gmail.com> wrote: > RPC serializes basic java objects and your javabeans > based on them, giving you a nice model for programming > since in GWT it's all Java when programming. If you > use HTTP, you can post name-value string pairs, and > then you'll have to process the response string. It's > just much less powerful, but may work fine for you. I > mean, the traditional web browser uses this technique, > but it does mean handling errors and URL encoding your > data to send and parsing the response. > > > > -- > > You received this message because you are subscribed > to the Google Groups "Google Web Toolkit" group. > To post to this group, send email to google-web- > tool...@googlegroups.com. > To unsubscribe from this group, send email to google- > web-toolkit+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit? > hl=en. > > > > > > -- > Lucas V. F. Ventura > Ciência da Computação - UFRJ > > > -- > > You received this message because you are subscribed to the > Google Groups "Google Web Toolkit" group. > > To post to this group, send email to google-web- > tool...@googlegroups.com. > To unsubscribe from this group, send email to google-web- > toolkit+unsubscr...@googlegroups.com. > 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 google-web- > tool...@googlegroups.com. > To unsubscribe from this group, send email to google-web-toolkit > +unsubscr...@googlegroups.com. > 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 google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
