Chris Withers wrote:
Tres Seaver wrote:
who's the CTO?
Jim is.
Okay, I get the joke now :-)
* "persistent" references are effectively required to be immortal:
it is _mandated_ that one be able to stringify the IOR, copy it
to a piece of paper, put the paper in a
Tres Seaver wrote:
who's the CTO?
Jim is.
Okay, I get the joke now :-)
* "persistent" references are effectively required to be immortal:
it is _mandated_ that one be able to stringify the IOR, copy it
to a piece of paper, put the paper in a bottle, and cast it on
the waves;
Evan Simpson wrote:
In the case of Catalogs, much of the time we're probably not interested in
cataloging "whatever lives at this path address";
At the moment this is true, but Jim and I have discussed the possibility
of ZCatalog being treating the paths less atomically and more as a
Michel Pelletier wrote:
At the moment this is true, but Jim and I have discussed the possibility
of ZCatalog being treating the paths less atomically and more as a
sequence of nodes from root to the target, this way, you could ask the
catalog for all objects below a certain point that match
- Original Message -
From: Chris Withers [EMAIL PROTECTED]
who's the CTO?
Jim Fulton, Chief Technology Officer.
use paths instead of object monikers.
Why not do both?
Have an POID (CORBA style) to actually identify an object and then use
paths of POIDS to identify stuff in a
Chris Withers wrote:
Hi,
I hope this is a stupid question but why does ZCatalog use the URL of an
object to uniquely identify it?
Because it's unique.
Why not just use a reference to the object?
How do you define that? If you mean reference in the strictly python
sense, then I