Franklin, thanks for your hints.
On 20 February 2012 20:08, Franklin, Matthew B. <[email protected]> wrote: >>-----Original Message----- >> >>we're currently in the process of starting to integrate OpenSocial >>into our application and I'm not sure which Shindig version would be >>best for later production use?! >> >>Is it safe to start integrating Shindig from SVN trunk at the moment >>(since there's no 3.0/2.5 release, yet)? Advantage would be that I can >>already start with OpenSocial 2.0 features. > > I know that there are quite a few implementers using trunk. We are currently > using Shindig 3.0 Beta 4 in Apache Rave (if I understand some of the rename > conversations correctly, this will become 2.5 when it goes for release) and > we haven't seen any major show stoppers yet. good to know. > As with any open source software, it is up to you (the implementer) to > determine what is suitable for your environment. Since I'm aiming for OpenSocial 2.0 compatibility of our product I'll stick with the trunk version at least until 2.5 is released. >>I'm trying to integrate Shindig into our software in a way that I can >>always upgrade it when new versions are released. Are there best >>practices for doing this? > > Internally, we try to handle this by keeping Shindig as isolated from our > core codebase as possible. We deploy it separately and try to wall off our > own custom pieces so that Shindig isn't too entrenched in our core > application. You can see how we have done this in Rave if you are > interested in following a similar approach: > http://svn.apache.org/repos/asf/incubator/rave. > > I am sure others on this list have more (and probably better) ideas. Thanks, I'll definitely take a look at Rave. I've grown confident now that it's possible to integrate Shindig without losing the chance for upgrades when new versions of Shindig or the OpenSocial specs are released. FWIW I'm also looking at how the guys of Eureka Streams integrated Shindig, quite nice project: http://www.eurekastreams.org/ Max
