Rev talk - Oct 2008 - wish list item: on_write_complete(you can set the number of bytes)

Twould be sure convenient for wanting to fill buffers before they
empty [for those of us paranoid the buffers will empty before we have
the chance to refill them.

I should hack on a C version of rev some time :) [C wrappers for
everything except the on_XXX methods, which, of course, call ruby].

-=R

another wish list item would <sigh> be the ability for it to just
write [in C] to some file and only report back "wrote X bytes" ...or
just report back when the connection is closed or something.  Might be
useful.
-=R

On Thu, Oct 23, 2008 at 3:52 PM, Roger Pack
<roger.pack at leadmediapartners.com> wrote:
> Twould be sure convenient for wanting to fill buffers before they
> empty [for those of us paranoid the buffers will empty before we have
> the chance to refill them.
>
> I should hack on a C version of rev some time :) [C wrappers for
> everything except the on_XXX methods, which, of course, call ruby].
>
> -=R
>


-- 
Thanks!
-=R

On Sat, Nov 1, 2008 at 11:08 PM, Roger Pack <
roger.pack at leadmediapartners.com> wrote:
> another wish list item would <sigh> be the ability for it to just
> write [in C] to some file and only report back "wrote X bytes"
...or
> just report back when the connection is closed or something.  Might be
> useful.
>
I''ve separated out the buffering code from Rev:

http://github.com/tarcieri/iobuffer/tree/master

That code is set up with pure-C routines for writing (or reading) as much as
possible to a non-blocking socket.  It''d be nice to integrate that (in
C)
with a libev watcher so the whole process never need call out to Ruby until
the actual callback method is being fired (i.e. a proactor)

--
Tony Arcieri
medioh.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/rev-talk/attachments/20081104/22ae6d86/attachment.html>