#1 Service Connection replacement

[Andrew Cuthbertson]

What does everyone think of this. Hopefully the formatting is
alright.

Currently a netlet can bind a service and get another
netlet.

+========+ +==============+
+ Client + --------> + Access
Point +
+========+ +==============+

If there was to be a
runtime code upgrade support for beatrix then all the access
points that are already connected will need to be shutdown and the
new access point with the updated code put in its place.

If the
client of this service doesn't cope with this problem by rebinding
the warrant then the service connection will be severed when the
netlet is shutdown and client will lose control of the
service.

If this was to be done now then this would take
place.

+========+ +==============+
+================+
+ Client + --> + Access Point + --> + New Code
+
+========+ +==============+ + Access Point +

+================+

but the original access point would need
to be kept around to keep the client's service connection
alive.

Unless the access point in the middle could replace it
's service implementation with the new code's implementation
then it could safely shutdown without the service connection
terminating.
X X
+========+ +====X===X=====+
+================+
+ Client + --+ + AccesX Point + -> + New Code
+
+========+ | +====X===X=====+ | + Access Point +
| X X |
+================+
+-------------------+

Any comments welcome.

Andy C