a class in the client sive can also be used in the server side...just make it implements Serializable and send it back to the server with the RPC services.
Also note that as the classes in the client package are going to become javascript, they don't implement all of the JRE. That may be also a factor to know if you should put this on the client package. On Wed, Jul 29, 2009 at 12:07 PM, maarten.de...@gmail.com < maarten.de...@gmail.com> wrote: > > Hi, > > I'm experimenting with GWT for a couple of weeks now and ran into > another question. > > The question relates where to put a certain class. Classes in the > client package are translated into javascript. Classes in the server > package are executed as java (I'm using App Engine too). Say I'm > building an app with a little game. I can write the game class at > client side so that that code can be run at the client, what seems to > be correct here. At the end of the game, the game should be persisted > into the datastore. So I make it persistence capable but than the > class is needed at the server side. > > What should I do now? Put it at server side and use it at client side > too? In that case, the class needs to be inherited in the .gwt.xml, > no? Or should I build two seperate classes: just send the data of the > game to the server and build the data store element from that data to > store it? > > Some advice would be appreciated :) > > Maarten Decat > > > -- Quer aprender a programar? acompanhe: Wants to learn GWT? Follow this blog -> http://tcninja.blogspot.com --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@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 -~----------~----~----~----~------~----~------~--~---
