Folks, I've been following this thread and I think we're missing an important part of the Honeycomb project proposal... the desire to create a fixed content storage capability for the OpenSolaris environment.
Note: It's cool that these folks initially delivered the functionality in an appliance form using Solaris. But that's not the primary reason for creating this new OpenSolaris project. The purpose of this project proposal is to extend the storage capabilities of the OpenSolaris environment to address a rapidly growing real-world problem -- write once, read many times data that requires additional metadata to describe, store and retrieve the data. Examples of this data and accompanying fixed content services include online photo repositories, medical records storage, university research data repositories, and online digital libraries. The fixed content storage capability consists of both client and server code. These folks would like to get the client interfaces out first for discussion followed by a slug of server code that implements the desired interfaces. There are communities looking to create standards for this type of data access -- snia.org with XAM and the Java community. There are also open source communities trying to build data management applications on top of fixed content data services such as fedora.info and dspace.org (both in the digital library content management space). Having an OpenSolaris project for fixed content storage services helps bring together the needs and conversations of these diverse communities... and will result in the first (I believe) open source implementation of fixed content storage software stack. I suggest that we ask our OpenSolaris storage community to weigh in as well on this project proposal since it's extending the storage capabilities of OpenSolaris. Lynn This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
