I've been toying with IMHO and managed to get past the outdated
documentation and even the examples work with small modifications :-).
Sessions are still a bit of a mistery, though. It seems that contrary
to my expectations URLs work across server restarts which is good. A
typical URL looks like this:
http://127.0.0.1/imho/my-app/qgnagsytcfeycsbh/no-caller/C2091/get-item?0
qgna... is the session id, but I don't understand what no-caller and
C2091 mean. If C2091 stands for a particular object in the given
session then how this does URL work accross restarts? Or does it? I am
bit confused.
Cheers, Gabor Melis
····@hotpop.com (Gabor Melis) writes:
> I've been toying with IMHO and managed to get past the outdated
> documentation and even the examples work with small modifications :-).
And what you are seeing isn't even the latest incarnation 8)
> Sessions are still a bit of a mistery, though. It seems that contrary
> to my expectations URLs work across server restarts which is good. A
> typical URL looks like this:
They don't work across restarts actually.
> http://127.0.0.1/imho/my-app/qgnagsytcfeycsbh/no-caller/C2091/get-item?0
> qgna... is the session id, but I don't understand what no-caller and
> C2091 mean. If C2091 stands for a particular object in the given
> session then how this does URL work accross restarts? Or does it? I am
> bit confused.
The URL is encoded:
<sessionid>/<calling-object>/<called-object>/<webmethod>?arg
So in this case, there is no calling object, and webmethod "get-item"
is to be invoked on object C2091.
--
Sincerely, Craig Brozefsky <·····@red-bean.com>
No war! No racist scapegoating! No attacks on civil liberties!
Chicago Coalition Against War & Racism: www.chicagoantiwar.org