Re: Caching within packages..

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Fri, 12 Dec 2003 16:37:53 -0800
Message-ID: <1071275778.879126@yasure>

Joachim Zobel wrote:

> On Thu, 11 Dec 2003 13:35:52 -0800, Daniel Morgan wrote:
>
>

>>NetComrade wrote:
>>
>>
>>>On Wed, 10 Dec 2003 17:48:48 -0800, Daniel Morgan
>>><damorgan_at_x.washington.edu> wrote:
>>>
>>>
>>>
>>>>So every time someone makes a change to a table you are going to bounce 
>>>>the server? Do you really advocate that? If so I'd suggest you keep 
>>>>really quiet during job interviews.
>>>
>>>
>>>Not necessarily 'bounce', more like a refresh (reconnect). Out app
>>>server is capable of that.. 
>>
>>Apparently you do not understand the concept that was described in the 
>>previous posts. What you propose will not work.

>
>
> The cached table is package state, which lives on a per session basis. So
> a reconnect will reload the cached table. What exactly do you mean by
> "will not work"?
>
> Sincerely,
> Joachim

Make a change to a table in one session and the in-memory table becomes invalid in every other session and you have no means of refreshing it other than bouncing every single user off the system every time that happens. I define that as "will not work".

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)

Received on Fri Dec 12 2003 - 18:37:53 CST