I would only use one service until it got "too big", or until your service calls fall into some sort of natural hierarchy, e.g., CustomerServices, OrderServices, etc. More Service classes mean more overhead in the web.xml, in the app xml file, etc. However, clarity of intent should be the guiding principle.
On Jan 12, 1:59 pm, Russ <[email protected]> wrote: > I have a single app that needs to call several different methods from > the server. > > Is it better to have all the methods contained in one RPC service, or > should I have a speerate service for each method? > > (By "Service" I mean the Service.java, ServiceAsync.java and > ServiceImpl.java files) > > Thank you.
-- 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.
