Question

When designing an application with a large number of remote services, is it better to have one RemoteServiceServlet end point with many methods or a large number of RemoteServiceServlet endpoints with fewer methods?

Was it helpful?

Solution

I would go with lots of RemoteServiceServlets, one per area of functionality or module in your application. Otherwise you end up with a "kitchen sink" of unrelated functionality all in one class.

OTHER TIPS

I am afraid that the question doesn't list the correct answer.

The command pattern offers you single end-point / single method solution for GWT-PRC.

Please see this presentation and you might find this out of the box implementation helpful.

I would suggest that you integrate your server side with some sort of dispatcher servlet like Spring, so you can ease the development, and then go with David Tinker's suggestion. You should design your app according to your functionalities.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top