On 24/04/2007, at 18:19, Gabriele Santilli wrote:
> > 2007/4/24, Henrik Mikael Kristensen <[EMAIL PROTECTED]>: > >> By the async sources, do you mean: >> >> http://www.rebol.it/giesse/async-protocol.r >> >> ? > > Latest one is: http://www.colellachiara.com/soft/libs/async-protocol.r > > It won't help much if Rugby is not using async-modes though. I'm inclined to do a rewrite of hipe.r as Maarten mentions on AltME: "If you use async:// you'll have to rewrite hipe.r and use Gabriele's do-after, do-every mezzanines as well. Would be great, because then there is a fully async Rugby and it *is* do-able. Kinda puts the stress on REBOL services. Note that the stub layer etc. will still work as that is decoupled from transport." as I'm constantly frustrated with the lack of async ability for properly displaying wait indicators and generally avoid program lock ups, particularly with get-rugby-service and with unreliable networks. But I'm afraid I haven't the foggiest idea how to do that. I'm looking at hipe.r, but it looks to me as if hipe is handling threading, ports, handlers and such in a way, that replacing it or rewriting it to use async:// doesn't add up for me. It seems I should attack a lower level than hipe, to do this. Any help would be appreciated. -- Regards, Henrik Mikael Kristensen -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
