On Thu, Apr 3, 2008 at 12:21 AM, Santiago Gala <[EMAIL PROTECTED]> wrote:
> > El mié, 02-04-2008 a las 22:44 -0700, Kevin Brown escribió: > > On Wed, Apr 2, 2008 at 9:20 PM, Raymond Auge <[EMAIL PROTECTED]> wrote: > > > > > The shindig plugin we developed works as a fire and forget app in all > > > the app server/servlet containers/RDBMS combinations that we support > > > (which is extensive, literally hundreds of combinations). > > > > > > What we're missing is that "injectable" datasource backend. > > > > > > Right now I'm flat out replacing the implementation of > > > > > > org.apache.shindig.social.opensocial.OpenSocialDataHandler > > > > > > overriding the implementations of the Basic*Services. > > > > > > But that's not a very nice way of working with it. At the very least > we > > > need some way to wire in an implementation. This way you could have X > > > backends bundled to handle the different possible scenarios, direct > > > JDBC, DAO Service Tier, RPC implementation, etc, while still allowing > > > for custom implementations. > > > > > > In our case, we're plugging in directly to our generated DAO service > > > tier, so as to leverage existing caching infrastructure, cluster > > > support, etc..., which means we'd want to implement the backend as a > > > custom code anyway. > > > > > > The question is "which is the most accepted way of building out these > > > plug-able backend implementations?" > > > > > > You can go anywhere from > > > - classNames as servlet init-params in the web.xml file > > > - classpath properties files specifying implementation classes > > > ... all the way to ... > > > - a Dependency Injection container like Spring... > > > > What about a URL mapping and json as data exchange language? This is > what CouchDB uses for DB mapping ;-) > > > > > The DI wiring is already started (as of about 5pm today), using Guice. > > Spring or other frameworks can be layered on top of this as appropriate. > > > > Again, though, this only satisfies the case of sites that are already > Java > > based. > > Yeah, people that got abducted into J2EE can't see other languages than > java. I was there but I'm slowly recovering :) > > I hope that shindig will be kept as simple as possible and do data > integration using Rest techniques or similar loose coupling. > > BTW, has anyone considered the Thrift podling starting recently at the > ASF for the RPC mechanisms? I'm not really sure how would it fit. It looks like it's just a proposal right now -- if it does indeed migrate from facebook to apache I think it's a logical choice for us. It seems to be based largely on a format virtually identical to the protocol buffer specification that has been discussed in numerous google published white papers (primarily the sawzall paper), so I'm sure it'll have a natural feel, and it's not that far removed from what we're trying to do with our shindig deployment at Google anyway. -- ~Kevin
