> I'd appreciate it if you can post another reply once you get back to the other
>machine. I'd like to believe there is a
> clean solution.
Absolutely.
> > Shouldn't it call into NewappUserPeer so you have the opportunity to
>override/extend that functionality? Does it not
> get the Peer to call into from TR.props? I'd answer these questions myself if I was
>at a different computer...
>
> I think you are right (and no, it doesn't get the peer to call from TR.props).
>While it looks like there is plenty of
> flexibility, it seems that there are a few pieces to the puzzle still missing.
>Another piece that is missing is a way
> to deal with the extensions to TURBINE_USER in such a way that some of the code to
>do this stuff is generated.
There is a security.peerclass property in TR.props.. Wish I could remember what it is
used for... I imagine the fulcrum package makes a bunch of this stuff easier..
Although I did get my stuff up and running in fairly short order.. not quite the way I
had envisioned it working.. but it did/does work.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
