On 26 août, 20:52, Christophe <[email protected]> wrote:
> I find the client-server distinction too coarse to work with. The
> strength of gwt is at least partly in the RPC mechanism and passing
> full classes.
...and those classes should generally be "DTOs" (a.k.a. "value
objects") and thus shouldn't have any embedded logic (even less some
logic that's only available on one side and not the other!)
(otherwise, you would be doing someObject.save(callback), not
myService.save(someObject, callback) !)
> I was therefore wondering. Isn't it possible to declare a specific
> function or inner class if that's easier to only be accessible on the
> server side ? I realize this poses all sorts of problems for variables
> and deciding whether or not something gets serialized, but I'd be most
> happy if the compiler just threw those problems in my face and
> expected me to fix them.
See http://code.google.com/p/google-web-toolkit/issues/detail?id=3769
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
