Get the real story via our monthly newsletter

Search

    2
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Apache Shindig: where does the portal end and the social application start?

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends

Enterprise Social Software Trends


Report Excerpt

The Enterprise Portals Report 2008 looks at... BEA AquaLogic User Interaction 6.1

"While some customers have opted to use ALUI for publicly-facing sites, the available portlets and nature of the architecture makes it hard to meet the needs of a high-performance or transactional website, where other products (including WLP) might be a better fit."

(p. 103)

More about The Enterprise Portals Report 2008

 

TrendWatch Blog

Apache Shindig: where does the portal end and the social application start?

20-Dec-2007

Last month, Apache member Brian McAllister proposed a new incubation project called Shindig, which would create an open source implementation of OpenSocial. OpenSocial is Google & Co's much hyped response to Facebook, offering a new common set of APIs for social applications across multiple websites.

To quote the interesting Shindig proposal:

    A social application, in this context, is an application run by a third party provider and embedded in a web page, or web application, which consumes services provided by the container and by the application host. This is very similar to Portal/Portlet technology, but is based on client-side compositing, rather than server.

Perhaps as a surprise to some, in particular outsiders to Apache, Shindig and Jetspeed (the official Apache Portal Project) are not connected in any way. For Apache this is the usual way of working: innovative, but often disconnected projects sometimes overlap or supercede each other. As another example, Jetspeed does not use Lenya, the Apache open source content management system. Rather Jetspeed works closely with Hippo, a Dutch open source Web CMS vendor.

Shindig could end up as the open source reference implementation for OpenSocial, but it is still very early days. Jetspeed has certainly not been as universally adopted as the famous Apache webserver. As an open source adherent, you should not assume a coordinated master plan among Apache projects and definitely not count automatic universal adoption for any tool that has the Apache moniker. At the same time, let's recognize that Shindig looks quite interesting, at the very least.

Thanks for Navaneeth over on The Portal Zone for picking up the story.

- Submitted by: Janus Boye, Contributing Analyst

All Portal Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us



Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

18113 Town Center Drive, Ste 217

Olney, MD USA 20832

1 800 325 6190 (N. America only)

+1 617 763 5336 (customer service)

+1 301 585 7004 (editorial)

Fax: +1 214 242 3048