> From: "WALLYWORLD" <ran...@[EMAIL PROTECTED]
>
> As i have now read and reviewed .. there are two types of
> connections to data, one is by the object, the other is by the
> attribute.
Would somebody please refer me to an explanation of this
distinction? I'm just guessing: If you have a bunch of terms to
narrow down what you are trying to refer to, that's just reference
by attribute(s), but after you connect to the FBI database or other
canonicalizer and obtain the unique ID such as social security
number then you can pretend you have reference by object, or do you
need to physically hold the object, as we've been unable to do with
Osama Bin Laden?
> I see you have suggested a shopping cart, where the contents are
> retained until the art is emptied, even between sessions.
This is a silly way of talking, because a HTTP session is a single
back-and-forth interchange, while a login sesson is one or more
HTTP sessions sharing a session cookie, and there might be other
sizes of session co-existing with those, so the word "session" by
itself is useless to say what you really mean.
Consider the case where you are shopping on behalf of several other
people, carrying several different shopping carts (one for each
person you're shopping for), all within a single login session of
your own, and at any time you can "check out" one of the carts and
have that batch of goods delivered while you are still shopping
with the other carts. Each cart has associated with it:
- Your own login ID (same for all these carts).
- ID of person you're shopping for (different for each cart).
- Shopping list for that person, with entrees that are somewhat
vague, like "bring back medium size package of baking soda",
which *you* must convert to UPC of item that can be purchased
- Ac***ulated actual items (UPCs thereof) so-far.
> i am myself trying to locate the instructions for registering a
> CLSID (class) so that i can try to call a program using CGI.
I don't quite understand why you need to do anything like that.
To set up a CGI program, you either have the application directly
as a script in the CGI file (typical way to do it in sh or perl),
or the application directly machine-executable (C, C++), or you set
up a sh script which launches the actual application (lisp, java).
Auto-loading of modules in lisp or java is part of the mechanism of
the language itself, having nothing to do with CGI. You just need
to make sure the classpath is correct in java, and that you have
autoload stubs in lisp.
|
