Francois PIETTE wrote: > About event handler: > We have the choice to enforce all are in sync or not. I'm not sure > yet what is best. At least it is easy to propagate all event handlers > to all component whichever subcomponent is used to assign the new > event handler. It is also very easy to have all subcomponent event > handler created equal to the main and let the user change it later. > Don't know yet what is better.
The latter is clearly better IMO. Otherwise it's not flexible enough and also requires that changing the event handler of any instance has to propagate to any other instance. > > About Addr/Port: > I agree with you. A new property "MultiListenAddrPort" has to be used > and all instance will get his own value assigned to his Addr and Port > properties. > > About persistent properties: > I don't understand the issue. There is, for instance, property SslEnable in TWSocketServer descendant TSslWSocketServer that is propagated to clients. Let's say you want two listeners /192.168.1.1:80/192.168.1.1:443 one SSL and one plain text. Then you have to set SslEnable property at run time. Steps required were iterate over the list of instances, find the one with Port 443 and set SslEnabled and perhaps SslMode as well. I also wonder when the instances specified by property "MultiListenAddrPort" will be created? -- Arno Garrels -- 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
