Re: [MirageOS-devel] towards a common Mirage 'FLOW' signature

[Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>]

On 12 Jun 2014, at 21:38, David Scott <scott.dj@xxxxxxxxx> wrote:

> I notice the low-level network APIs (NETWORK, ETHIF, ...) are *almost* like 
> this except they have a function like
> 
> val listen: t -> udp:callback -> tcp:callback -> ... 
> 
> Perhaps later (V2, V3?) we could split this into something like a 
> 
> val read: t -> buffer (* satisfy FLOW *)
> val classify: buffer -> [ `UDP; `TCP ]
> 
> -- is that a good idea?

i generally like the idea of doing something other than an ad hoc collection of 
callbacks.

how would the scheme above handle recursive protocols (IP-in-IP etc)?

(probably irrelevant but fwiw: i tried doing something a little like this with 
the pcap code -- so there was a set of default "demux" functions but you could 
override them all to construct your own protocol demux dag.)


-- 
Cheers,

R.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel