[railroad-dev] Railroad features for Plone developers?

[Guido Goldstein]

Hi!

Sorry for the late reply.

Julian Davison wrote:
> Guido Goldstein wrote:
[...]
>> But the whole database story will change.
>> Trust me, I've insider infos on that. :)
> 
> 
> Anything you can share as to how that's going to change? :)

We're developing a backend w/o the PostgreSQL dependency.
We encountered some non-technical hmm... challenges with PostgreSQL,
so we decided to try something that doesn't need a RDBMS.

We decided to use BSDDB -- the Sleepycat variant --, mostly
because it's integrated w/ Python already. [1]

The code is in the svn under the gst-bsddb branch.
But this is really not for public consumption, at the moment.


>> Another, for now not very prominent, feature is that you can share the
>> resources between different clients, including the meta-data.
>> But this is really a different story ...
> 
> 
> That's the other attraction to us, though the current
> authentication scheme needs to change a little.
> I've not thought it through (at all) fully, but we need
> railroad to auth back to the requesting client, rather
> than the 'owner' client.

Hmmm... this would mean to lookup the requesting ip/hostname and
check it against the registered clients.
Should be solvable.
But I can't do it at the moment. Sorry.
OTOH, if you want to dig into the code, I'll be happy to help you.

Btw, can you give me a hint on why you want the authorization this
way?

Cheers
  Guido G.

[1] Since 2.3 there is the bsddb module in the standard library.