Re: Netgraph feature request/suggestion

2001-09-26 Thread Maksim Yevmenkin
Julian, [...] > All this changes in -current where netraph was largely rewritten. i know. i'm using current > > i'm in the middle of the project that uses Netgraph. > > everything is going pretty good, but there is one small > > issue. in five words it is "message and data delivery > > schedu

Re: Netgraph feature request/suggestion

2001-09-26 Thread Julian Elischer
Hi! I'd love to hear more about what you are doing.. but to answer your questions.. Note: All this changes in -current where netraph was largely rewritten. On Wed, 26 Sep 2001, Maksim Yevmenkin wrote: > Hackers, > > i'm in the middle of the project that uses Netgraph. > everything is going

Re: Netgraph feature request/suggestion

2001-09-26 Thread Maksim Yevmenkin
Luigi, [...] > one problem you have to keep in mind with what you want to do > (and i am not talking about the implementation that you suggest, > just the "delayed processing" aspects) is that sometimes data passed > through modules have a limited lifetime and might have become stale > by the ti

Re: Netgraph feature request/suggestion

2001-09-26 Thread Luigi Rizzo
Hi, one problem you have to keep in mind with what you want to do (and i am not talking about the implementation that you suggest, just the "delayed processing" aspects) is that sometimes data passed through modules have a limited lifetime and might have become stale by the time the consumer is s

Netgraph feature request/suggestion

2001-09-26 Thread Maksim Yevmenkin
Hackers, i'm in the middle of the project that uses Netgraph. everything is going pretty good, but there is one small issue. in five words it is "message and data delivery scheduling". here is an example: Node A --> Node B --> Node C Node "A" forwards data/messages to Node "B" and Node "B"