[835] in Coldmud discussion meeting

connections

daemon@ATHENA.MIT.EDU (Wed Oct 18 15:00:01 1995 )

Date: Tue, 17 Oct 1995 13:48:21 -0600
From: 869683 Gillespie Brandon James <brandon@nibley.declab.usu.edu>
To: coldstuff@pippin.ece.usu.edu

Right now it is possible to have more than one connection sending/receiving
with an object.  For various reasons I am changing this, what I want to
know is:

   When a new connection attempts to 'bind' to an object, should we:

       1: close the older connection, perhaps call obj.abort (or similar)
       2: deny the new connection

I can see advantages with both, if your db is not functioning correctly
and you accidentally try to bind a new connection to an object already
serving a connection, the old one would get bumped, possibly disconnecting
the developer.  Of course, this is a rare case and is due to bad coding
on their behalf anyway.

I will probably do #1

The main reason is that for cleanliness I only think you should have one
connection per object, it is cleaner this way...

-Brandon