Ty Sarna wrote:

> Unfortunately there are a lot of things that Zope just can't do because
> there is no way to get a persistent "ticket" for an object that can be
> handed out to some external system, and then later redeemed for the
> (properly wrapped) object. Pathnames are not useful, because they don't
> last for the object's lifetime.

Hmmm ... what you describe sounds a lot like an ILU "string 
binding handle" -- see


ILU does have a Python binding, and I've been thinking that ILU 
and Zope might have a lot of potential if used together ... it 
could make Zope "multi-lingual" .... :^)  Has anyone thought of 
doing anything with the two together?  

-- Steve.

                                           oo _\o
                                            \/\ \
____________________________________________ oo _________________
"Sometime you're the windshield; sometime you're the bug."
- Knopfler

Stephen C. Waterbury                       Component Technologies
Code 562, NASA/GSFC                  and Radiation Effects Branch
Greenbelt, MD 20771           Engineering Web/Database Specialist
Tel: 301-286-7557                              FAX:  301-286-1695        
WWW:          http://misspiggy.gsfc.nasa.gov/people/waterbug.html

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to