On 2016-10-28 09:09, Nick Patavalis wrote:
On Fri, Oct 28, 2016 at 8:15 AM, Peter Mogensen <a...@one.com> wrote:
The point being that it's up to the user of the interface how to specific
Server implementation should work.
Yes, of course, but an interface with just two methods (Serve / Stop)
is not enough to provide race-free semantics (unless you disallow
restarting a stopped server).
Checked my code... I do believe you are right...
More specifically: A set of Server objects are handled by a "master"
server. I don't care that much about a Shutdown() signal being lost to
the master server, but I do care about either none, or all of the
Servers managed being shut down.
It seems there is indeed the off chance that a Shutdown() quickly
following a Serve() call might be dropped by one of the servers, but not
the rest. ... leaving that server still running after the rest are shut
down.
/Peter
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
