2008/3/26, Kevin Brown <[EMAIL PROTECTED]>: > Might I pester some of you guys for feedback on this? I'm looking for a few > things: > > Non-committers (and "ordinary" users): > 1. Do you think that writing a Guice module is easier than writing your own > custom CrossServletState? (If you've done neither, then you probably don't > care about the change anyway).
Do we ordinary users need to write our own CrossServletState? My assumption is that an Ordinary user must at some point to branch, in order to provide the particulars of an application: this should be (besides some javascript and raw html for our own webserver) basically an implementation of the login/ID process and an implementation of the opensocial database. In fact the actual CrossServletState does not worry a lot about the injection of database things into the social objects, so the only points an end-user would like to modify are the default paths and this question of identification of an user (and, then, storage of gadget defaults) What I would thank is an arrangement allowing for this branching (and the one of the opensocial database handlers) in separate folders respect to the main development, so that I can keep doing svn update of the rest of the shindig as it evolves, and keep the development of my databases at their own speed. The less svn update conflicts I must to solve, the best. Alejandro
