Re: [Zope-dev] Unique and Contant object IDs
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 http://www-db.stanford.edu/~testbed/ilu/ilu20doc/manual_1.html#SEC10 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? Cheers, -- 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] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Meaning :-S
Chris Withers wrote: > > Ken Manheimer wrote: > > > > Python Zopelet > > Perl Zopelet > > XSLT Zopelet > > > > Zope-specific, runs on the server, shows the implementation language, > > won't be confused with non-remotely-editable functions, methods, scripts, > > code in general. > > ... Zopelet means absolutely nothing, and will just add to > confusion :-( I agree with Ken: I think it's a good choice because it *is* Zope-specific -- I think Zope should be in the name. If you are using Zope, it will be meaningful; if not, it won't -- and shouldn't be. I also think "Zopelet" does not "mean absolutely nothing" in terms of connotation -- it carries the connotations that Ken mentioned, which is good. My $0.02. -- 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] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Python and Perl scripts
Michel Pelletier wrote:
>
> [EMAIL PROTECTED] wrote:
> > descriptive. Widget has technical meaning. Perhaps task or job are
> > suitable, as in
> > Safe Python Task
> > Safe Python Job
> > Safe Python Subtask
> > Safe Python Function
> > Safe Python Script
> >
> > Then external methods, which are often also not methods, can become
> > Flexible Python Task
> > Flexible Python Job
> > Flexible Python Subtask
> > Flexible Python Function
> > Flexible Python Script
> >
> > But if you really want to use
> > Tame Snake Thingy, and
> > Wild Snake Thingy,
> > go ahead, but please do not credit me in the documentation!
> Documents, Templates and Scripts
> or
> Documents, Templates and Methods
I REALLY like Thingy! And a very Pythonesque choice it would
be ... :^) Python Thingies and Perl Thingies. How nice to be
so connotationless! ... but maybe not so connotationless ...
recalling the usage of "thingy" in the Python, Monty oeuvre
("YOU know ... THINGY!!") ... you might want to consider
Tame Snake Sex, and
Wild Snake Sex,
so then you have
Documents, Templates, and Sex
Python Sex vs. Perl Sex? ... wow, just think of it!
Of course, alibis about working late would have to be
carefully worded ...
Sorry ... it's late on a Friday ... but I DO like Thingy! :^)
Cheers,
-- 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]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
