From: SourceForge.net <no...@so...> - 2004-12-30 00:43:40
|
Feature Requests item #1093037, was opened at 2004-12-30 00:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=1093037&group_id=10894 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Roy E Terry (royterry) Assigned to: Nobody/Anonymous (nobody) Summary: Guarantee socket channel name unique Initial Comment: In a dynamic server/monitor app I have many socket connections being created and eventually closed. Each connection represents some system component process that needs to be monitored. I find on Windows that the socket string "sockNNN" is often reused. If each connection got a unique socketNNN* the managing logic could be quite a bit simpler as it could use the socket channel handle as representing a unique connection instance. I suppose wrap-around at 2^31 would not realistically effect the code. Canvas ID's currently follow this sort of uniqueness rule and it is indeed helpful. Roy ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=360894&aid=1093037&group_id=10894 |