[<<][packetforth][>>][..]
Sun Apr 22 14:30:10 CEST 2007

time for pf again

need to fix some things, but first i need to figure out how tasks
work. most of the code is in scripts/scheduler.pf

a task has independent return and data stacks.

the udp stuff apparently returned just a single list.


question: does it make sense to have udp connections respond to
connection refused errors? (from ICMP port unreachable).


ok, something for the list of rules: the interface in pf for reading
messages is either:

* a task which handles one at a time, and blocks when done
* a function that returns the list of pending messages

blocking the entire app is depricated, but i think should still be
possible in terms of the other 2.

faking blocking i/o: just yield if something's not ready.





[Reply][About]
[<<][packetforth][>>][..]