On Tue, 5 Nov 2002, Maksim Yevmenkin wrote:
> Archie Cobbs wrote: > > > > Maksim Yevmenkin writes: > > > I would like to get some feedback on the idea i have. > > > Basically i would like Netgraph system to send kevents > > > whenever something happens. For example: > > > > > > 1) node X of type Y was created/destroyed > > > 2) hook X was connected/disconnected to/from node Y > > > 3) Data passed via hook X > > > 4) Node X got message Y > > > > This would be nice, but what does kqueue() really have to do with it? > > > > I.e., why not just allow the creation of a ng_monitor(4) (or whatever you > > want to call it) node, which would send out event report messages to > > whomever connected to it. > > common interface? reusing existing functionality? just open a > Netgraph socket, register for events and away you go. > > and you are right ng_monitor (or whatever) is another way to > do the same thing. A program would only have to look for one kind of event with kqueue. otherwise it's have to check with kqueue NAD teh ng_monitor node. Its possible BOTH approaches could be combined.. Most of teh event catching code would be shared. > thanks, > max > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
