This design would not break any existing code and would ease using
the new multiple listen easy to implement in higher level components.
It won't break existing code, but remains a hack IMO.
I don't agree with you. Please explain.
All event assignments and unassignments have to be kept in sync.
They will be easily with setter and getter.
Also I would not bind the construction/destruction of the additional
instances to the Addr string property (grrr),
Why "grrr" ? Please explain.
instead let the user explicitly create additional server instances.
That could be, for instance, a method like:
"TWSocketServer.AddServer(
const AServerClass: TWSocketServerClass; const AAddr: String; APort:
String;
AListenBackLog: Integer): TWSocketServer; virtual;"
Such a method could complement the design I suggested, updating the addr and
other properties.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
