Hello Ben,
Friday, November 7, 2003, 2:53:09 PM, you wrote:
B> If the table doesn't have to be 100% accurate, you could always timestamp
B> the rows and have connected clients update their row, while old rows get
B> reaped periodicaly.
I was hoping for a more natural solution. Implementing a heartbeat in
the application is a complication I'd like to avoid at all cost.
-Boris
B> On Fri, 7 Nov 2003, Boris Popov wrote:
>> I do want them to be visible to everybody. This is a sessions pool,
>> where sessions are inserted when our app connects and removed when it
>> disconnects, however this would only work for graceful disconnects,
>> which we all know isn't always the case. So I want a table that is
>> somehow notified of a session disconnect and deletes rows created by
>> that session.
>>
>> Any ideas?