Hi all, so let's be more concrete:
here is a first temporary freehand sketch of the 'event crossbar switch': http://trac.ict-ok.org/browser/documentation/temporary/20070917_queue01.pdf even more concrete for Obj1 and Obj3: Obj1 should be an UPS. the signal shoul be 'battery empty/shutdown now' Obj3 should be a server. The user can configure an additional short connect between Obj1 and Obj4. This will shutdown Obj4 (e.g. another server) on next 'battery emplty'-event, too. I'm working on this within the next few days - anybody additional ideas or 'wishes'? Markus ps. e.g. an early definition of Obj1 will be: http://trac.ict-ok.org/browser/trunk/org/ict_ok/components/host/special/mge_ups/interfaces.py Am Dienstag 19 Juni 2007 um 23:30 Uhr schrieb Stephan Richter <[EMAIL PROTECTED]>: > On Monday 18 June 2007 18:30, Markus Leist wrote: > > When the registration of an event between the objects and > > the utility is bidirectional, this utility is some kind of > > "event crossbar switch" like > > > > obj 1 <-> <-> 0 > > obj 2 0 0 <-> > > obj 3 0 <-> 0 > > obj a obj b obj c > > > > which _dynamically_ can be configured through the web. > > (some other aspects are routing, metric/priority, detection > > of event cycle ...) > > > > Is there some piece of code? Any ideas? > > I really have no idea what you are talking about. You have not defined obj 1, > obj 2, obj 3. Also, what does "<->" mean? > > I think a very concrete example would be best. _______________________________________________ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
