[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Remove DEVICE.connect?



On Thu, Jan 22, 2015 at 11:04 AM, Thomas Gazagnaire
<thomas@xxxxxxxxxxxxxx> wrote:
>>> So, I propose removing connect from the type signatures (but keeping
>>> it in the implementations). Then, being given a device only implies
>>> the ability to use it, not the ability to create more devices.
>
> Can you still easily compose devices together if you don't have a way to 
> connect? Who will be responsible for calling the implementation-dependant 
> connect function? Only the mirage tool in main.ml? (I guess that's already 
> the case)

Not quite - for example `Tcpip_stack_direct.Make(...).connect` calls
the `connect` of its arguments, which are only known by their
signatures.  But it would be easy for the mirage tool to generate code
to make these calls and pass their results to the `connect` of the
stack.

In general I think this is an excellent idea!  I will gladly help make
this change as soon as I'm done with the configuration keys stuff.

Cheers,
Nicolas

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

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.