Re: [GNUnet-developers] Asynchronous IO in Rust

[Jeff Burdges]

On Thu, 2017-03-23 at 21:58 +0100, lurchi wrote:
> > > Did I understand it correctly that modifying the GNUnet scheduler
> > > means
> > > you're planning to not do IPC with the GNUnet services from Rust
> > > anymore? That would be good news to me because it's easier to
> > > maintain
> > > the Rust bindings when they call the API functions (which are
> > > supposed
> > > to change rarely).
> > 
> > No.  Ain't necessarily so easy to analyze the memory safety of any
> > given
> > C API that uses the GNUnet scheduler.  This might remain problematic
> > even if the GNUnet scheduler were running on top of mio, tokio,
> > etc.  
> 
> I think I don't understand. If all the client parts are reimplemented
> in Rust and communicate directly with the services via IPC (as done in
> the current gnunet-rs implementation), what do we need the GNUnet
> scheduler for? Then everything client-side would be scheduled directly
> by the tokio event loop, wouldn't it?

Yes, but maybe I did not understand your question.  You said "you're
planning to not do IPC with the GNUnet services from Rust", which only
really parses as "you are planning to do IPC with the GNUnet services
only via C", nd that seemed consistent with your worry about API
functions changing. 

Jeff

signature.asc
Description: This is a digitally signed message part