yo!
> Consider the following:
> Client requests entity with PK Foo
> Server loads Foo and creates tmp key 17
> Client calls Foo/17
> Server passivates entity with key Foo/17
> (and here is the problem)
rickard it's runtime!!!
the moment you passivate I drop key 17...
> Since server cannot keep the entire map of fastkey->key mappings
> in-memory (would NOT work with lots of entities during an extended
> period of time) it will have to be dropped.
already done
> Client calls Foo/17. Server says "huh? I have no idea what PK 17 maps
> to.. sorry"
hee hee here is what you miss... the client calls with PK Foo and 17.
server says (I am coding it) 17? I don't know about 17... do I know about PK
Foo?
(yes it does) and there tada... we are back to the current situation we work
from PK Foo.
>
> That is the problem. So, you do indeed have to store the mapping between
> the fastkey and the real key. How do you intend to do that?
>
> > doing it...doing it...
>
> NO DON'T DO IT.
>
> > it's pretty simple too
>
> I KNOW. But you're shooting yourself in the foot.
grab some coffee sit down, track speed problem, wait
marc
>
> /Rickard
>
> --
> Rickard �berg
>
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
>
