You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Mike Murray <as...@gmail.com> on 2006/08/12 20:22:56 UTC
New storage implementation for Slide
Hello everyone,
I am the project manager for a distributed redundant network data storage
system called Rings.
I was curious about how one would go about constructing a new data storage
implementation for slide so that, instead of using an SQL database, it could
use this network data storage system that we are developing. The data
storage system is similar to a relational database, but there are some key
differences.
Which classes or interfaces would have to be implemented and how much
documentation is available on this?
Could anyone estimate the cost (developer hours) of doing this?
If someone on this list is interested in actually helping to write the code
for this, I can send the documentation for our tool (not yet publicly
available) and add a user to CVS.
Let me know if you are interested / can help.
-mike
Re: New storage implementation for Slide
Posted by Oliver Zeigermann <ol...@gmail.com>.
Hi Mike!
You need to implement
NodeStore, LockStore, RevisionDescriptorsStore,
RevisionDescriptorStore, SecurityStore and ContentStore
from package
org.apache.slide.store
Have a look at
org.apache.slide.store.txfile.TxFileContentStore
and
org.apache.slide.store.txfile.TxXMLFileDescriptorsStore
or
org.apache.slide.store.impl.rdbms.AbstractRDBMSStore
as a reference.
HTH and cheers
Oliver
2006/8/12, Mike Murray <as...@gmail.com>:
> Hello everyone,
> I am the project manager for a distributed redundant network data storage
> system called Rings.
> I was curious about how one would go about constructing a new data storage
> implementation for slide so that, instead of using an SQL database, it could
> use this network data storage system that we are developing. The data
> storage system is similar to a relational database, but there are some key
> differences.
>
> Which classes or interfaces would have to be implemented and how much
> documentation is available on this?
> Could anyone estimate the cost (developer hours) of doing this?
>
> If someone on this list is interested in actually helping to write the code
> for this, I can send the documentation for our tool (not yet publicly
> available) and add a user to CVS.
>
> Let me know if you are interested / can help.
>
> -mike
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: New storage implementation for Slide
Posted by Mike Murray <as...@gmail.com>.
The specification is in progress, and I am hesitant to send what we have so
far, as it is only the first two parts, which don't actually have much to do
with the data storage mechanism. Completion of the specification is expected
on September first and I will forward a PDF copy to the mailing list at that
time. I have javadoc generated documentation, but this will be of no help
without the specification.
The product is very similar to JXTA, from what I hear about that tool.
The software is already implemented, but we don't feel comfortable putting
it out there completely undocumented, so we are now in the process of going
back and describing in detail how we arrived at the product.
Rings is proprietary software, but any webdav/slide plugin would be publicly
available, open source, and resellable. I would be willing to contribute to
the development of this plugin as much as I can with my limited knowledge of
webdav. I am certainly available to answer questions about rings 24 hours a
day.
I am also willing to make minor (and even major) modifications to rings to
make this plugin work well, as it is somewhat important to our popularizing
this tool outside of academia.
I look forward to working with you and your team, Michael.
See you in September.
-mike
On 8/13/06, Michael Oliver <ol...@alariussystems.com> wrote:
>
> We would be interested if Rings has merit, which I assume it does.
>
> We have already written a distributed version of Slide using a JXTAStore
> that is a secondary store that raises a advertisement when a resource
> changes and the JXTA Peer Store picks up that advertisement and
> synchronizes
> the resource using WebDAV.
>
> If your Rings fit in with that we wouldn't mind sharing back as long as we
> can resell the code with our solutions.
>
> Michael Oliver
> CTO
> Alarius Systems LLC
> 6800 E. Lake Mead Blvd, #1096
> Las Vegas, NV 89156
> Phone:(702)866-9034
> Cell:(518)378-6154
> Fax:(702)974-0341
>
> -----Original Message-----
> From: Mike Murray [mailto:ashesfall@gmail.com]
> Sent: Saturday, August 12, 2006 12:23 PM
> To: slide-user@jakarta.apache.org
> Subject: New storage implementation for Slide
>
> Hello everyone,
> I am the project manager for a distributed redundant network data storage
> system called Rings.
> I was curious about how one would go about constructing a new data storage
> implementation for slide so that, instead of using an SQL database, it
> could
> use this network data storage system that we are developing. The data
> storage system is similar to a relational database, but there are some key
> differences.
>
> Which classes or interfaces would have to be implemented and how much
> documentation is available on this?
> Could anyone estimate the cost (developer hours) of doing this?
>
> If someone on this list is interested in actually helping to write the
> code
> for this, I can send the documentation for our tool (not yet publicly
> available) and add a user to CVS.
>
> Let me know if you are interested / can help.
>
> -mike
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
>
RE: New storage implementation for Slide
Posted by Michael Oliver <ol...@alariussystems.com>.
We would be interested if Rings has merit, which I assume it does.
We have already written a distributed version of Slide using a JXTAStore
that is a secondary store that raises a advertisement when a resource
changes and the JXTA Peer Store picks up that advertisement and synchronizes
the resource using WebDAV.
If your Rings fit in with that we wouldn't mind sharing back as long as we
can resell the code with our solutions.
Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)866-9034
Cell:(518)378-6154
Fax:(702)974-0341
-----Original Message-----
From: Mike Murray [mailto:ashesfall@gmail.com]
Sent: Saturday, August 12, 2006 12:23 PM
To: slide-user@jakarta.apache.org
Subject: New storage implementation for Slide
Hello everyone,
I am the project manager for a distributed redundant network data storage
system called Rings.
I was curious about how one would go about constructing a new data storage
implementation for slide so that, instead of using an SQL database, it could
use this network data storage system that we are developing. The data
storage system is similar to a relational database, but there are some key
differences.
Which classes or interfaces would have to be implemented and how much
documentation is available on this?
Could anyone estimate the cost (developer hours) of doing this?
If someone on this list is interested in actually helping to write the code
for this, I can send the documentation for our tool (not yet publicly
available) and add a user to CVS.
Let me know if you are interested / can help.
-mike
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org