[railroad-dev] Railroad features for Plone developers?

[Julian Davison]

 > The installation went quite smoothly, but now we are
 > wondering how can RailRoad help us. We are using Plone LDAP
 > authentication, so we would not need RailRoad server auth
 > feature, and we are going to use Plone to store and search
 > the meta-data, so we do not need the SQL feature.

The Railroad-auth is aimed at ensuring only authorised users
can access the data stored in the Railroad repository. (Since
users make requests directly to Apache, and not through Plone)
The meta-data available on the Plone (Railroad) Proxy objects
are (or can be) stored in an SQL database.

 > Which additional features, beside establishing a relationship
 > between an archetype based content-type and a webdav
 > repository, RailRoad offers to help Plone developers to built
 > webdav-based media libraries?

I've always viewed Railroad as, primarily, being a simple and effective,
way of combining the advantages of serving large, static, content
from Apache (v2) with the advantages of workflow/interface offered
by Plone. (The workflow is a key aspect of our application requirements)



J,