Pluggable helpers planned for 2.x

[Jason Coward <dr...@cox-internet.com>]

Remy:

I am working for an Enterprise Portal company that is very interested in
integrating Slide as a content management module for a reference implementation.
I am tasked with evaluating Slide and how it might be integrated with our
existing portal software and noticed that in the current status document, it
says that the "helpers" will be made pluggable in version 2.x.  Does that mean
that we could not take Slide 1.x and reimplement the low-level service modules
against our product's metadata infrastructure (security, etc.)?  Or am I missing
the point?

Also, is there any published schedules or timelines for release of the Slide 1.x
beta, or estimates for release of Slide 2.x?

Thanks,

Jason Coward
Mongoose Technology, Inc.
Technical Relationship Manager
http://www.mongoosetech.com

Re: Pluggable helpers planned for 2.x

[Remy Maucherat <re...@apache.org>]

> Remy:
>
> I am working for an Enterprise Portal company that is very interested in
> integrating Slide as a content management module for a reference
implementation.
> I am tasked with evaluating Slide and how it might be integrated with our
> existing portal software and noticed that in the current status document,
it
> says that the "helpers" will be made pluggable in version 2.x.  Does that
mean
> that we could not take Slide 1.x and reimplement the low-level service
modules
> against our product's metadata infrastructure (security, etc.)?  Or am I
missing
> the point?

I think there is a confusion between a Helper and a Store.

- A helper is actually a part of the Slide API the client will use. It
provides high level functionality, and is not pluggable (yet). Example : The
security helper provides API calls to check if principal 'foo' has the right
to do action 'bar' on object 'foo2'. Making the security helper pluggable
would enable you to replace the ACL checking algorithms used  for every
security check in Slide.
- A store is a low level service which responsability is to handle the
storage of a specific type of objects. This IS pluggable. Example : A
security store is responsible for storing NodePermission objects. Nothing
more, nothing less. You can implment a security store which would store
these objects on the filesystem and have Slide use that new store.

> Also, is there any published schedules or timelines for release of the
Slide 1.x
> beta, or estimates for release of Slide 2.x?

Each time I feel I'm close to beta, I add a new (important) feature.

I can give no estimates yet for Slide 2.x.

For Slide 1.x beta here's the planning :
- finish the JTA stuff, then release M6 (it may happen today)
- implment DAV ACL both on the client and the server, then release M7
- release a M8 if additional features are added, or if showstopper bugs are
found
- tweak more, and then release a beta

Remy