[comp.protocols.appletalk] MacTCP never releases server assigned IP #'s.

mlwiese@athena.mit.edu (Michael L Wiese) (06/30/89)

Looking through MacTCP docs I received from APDA recently, I read that the
first application to initialize MacTCP will cause an IP address to be acquired
using KIP (if you're configured to use KIP dynamic IP assignment.) Since
multiple apps running under MultiFinder may all use MacTCP services, quitting
from one of them should not close MacTCP. So apps are not allowed to close
MacTCP when exiting, and MacTCP keeps the IP address alive until shutdown.

This means I now need to take up one slot of IP address space for each Mac,
instead of just getting enough addresses to meet the peak demand.

Wouldn't it be possible for apps to 'check in' when they need TCP services,
and 'check out' when they are finished, so that MacTCP could release its
IP address when all apps have 'checked out'? Of course this would only
work if all apps exited properly, but at least the potential would be there.

Mike Wiese
mlwiese@athena.mit.edu