Status: New
Owner:
[hidden email]
Labels: Type-Review Priority-Medium
New issue 4428 by
[hidden email]: New mechanism for Zinc servers'
start/stop handling after system startUp/shutDown
http://code.google.com/p/pharo/issues/detail?id=4428After a discussion started with this email:
http://lists.gforge.inria.fr/pipermail/pharo-project/2011-May/049226.htmlI implemented a new mechanism for Zinc servers' start/stop handling after
system startUp/shutDown:
Sven Van Caekenberghe uploaded a new version of Zinc-HTTP to project Zinc
HTTP Components:
http://www.squeaksource.com/ZincHTTPComponents/Zinc-HTTP-SvenVanCaekenberghe.169.mcz==================== Summary ====================
Name: Zinc-HTTP-SvenVanCaekenberghe.169
Author: SvenVanCaekenberghe
Time: 19 June 2011, 2:21:38 pm
UUID: ebc443eb-7ce9-488c-92cb-05a67179c4f4
Ancestors: Zinc-HTTP-SvenVanCaekenberghe.168
implementation of a new mechanism for system #startUp/#shutDown handling by
ZnServer(s):
ZnServer holds a class variable ManagedServers, clients can
#register/#unregister to receive #start/#stop when the system
#startUp/#shutDown is sent;
currently only the default server (of which there is only one instance per
ZnServer subclass) is automatically registered/unregistered in #defaultOn:
and #stopDefault,
other instances must do this explicitely themselves
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker