> I think that's a reasonably simple API and one that allows you to do anything
> you want without introducing some extra interfaces that notify observers
> have to implement, just requiring that they are callable.
Yeah, thats fine. So
+ all observers registered on a connection would get notified when a notification
on that connection arrives.
+ a dispatching scheme based on channel can be built on top of above
+ the LISTEN/UNLISTEN is orthogonal to observer registration
+ any callable which takes a first positional argument of type "notify" can be used
+ the whole interface for above is Connection.addNotifyObserver/removeNotifyObserver
, right?