So here's a start (patch below) to streamlining the way shindig works with rpc and rest endpoints. I did this so I could batch gadgets and social calls in the same request.
Using Guice Multibindings it's easy to support a set of bindings that spans multiple modules. Each module can add it's own implementations to set. This would then allow for a single /rpc and /rest endpont which could allow for a flattened URL structure like so: /rpc /rest /ifr /oauth /js /proxy /concat /oauthcallback /accel # legacy /makeRequest /metadata Is anyone deeply attached to /social and /gadgets? ---------- Forwarded message ---------- From: <[email protected]> Date: Tue, May 11, 2010 at 6:57 PM Subject: merge together social/gadgets rpc/rest endpoints (issue1169044) To: [email protected] Cc: [email protected] Reviewers: shindig.remailer_gmail.com, Please review this at http://codereview.appspot.com/1169044/show Affected files: M java/gadgets/src/main/java/org/apache/shindig/gadgets/DefaultGuiceModule.java java/server/src/main/webapp/WEB-INF/web.xml M java/server/src/test/java/org/apache/shindig/server/JettyLauncher.java M java/server/src/test/java/org/apache/shindig/server/endtoend/EndToEndServer.java M java/social-api/src/main/java/org/apache/shindig/social/core/config/SocialApiGuiceModule.java M java/social-api/src/test/java/org/apache/shindig/social/SocialApiTestsGuiceModule.java M java/social-api/src/test/java/org/apache/shindig/social/dataservice/integration/AbstractLargeRestfulTests.java
