From roger.pack at leadmediapartners.com Sun Nov 2 01:08:57 2008 From: roger.pack at leadmediapartners.com (Roger Pack) Date: Sat, 1 Nov 2008 23:08:57 -0700 Subject: [Rev-talk] wish list item: on_write_complete(you can set the number of bytes) In-Reply-To: <966599840810231552t12490450gbc716719b236125f@mail.gmail.com> References: <966599840810231552t12490450gbc716719b236125f@mail.gmail.com> Message-ID: <966599840811012308k37dd0085s94e46d9a5fcdc562@mail.gmail.com> another wish list item would 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 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 From tony at medioh.com Tue Nov 4 14:40:05 2008 From: tony at medioh.com (Tony Arcieri) Date: Tue, 4 Nov 2008 12:40:05 -0700 Subject: [Rev-talk] wish list item: on_write_complete(you can set the number of bytes) In-Reply-To: <966599840811012308k37dd0085s94e46d9a5fcdc562@mail.gmail.com> References: <966599840810231552t12490450gbc716719b236125f@mail.gmail.com> <966599840811012308k37dd0085s94e46d9a5fcdc562@mail.gmail.com> Message-ID: On Sat, Nov 1, 2008 at 11:08 PM, Roger Pack < roger.pack at leadmediapartners.com> wrote: > another wish list item would 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: From tony at medioh.com Wed Nov 5 17:13:03 2008 From: tony at medioh.com (Tony Arcieri) Date: Wed, 5 Nov 2008 15:13:03 -0700 Subject: [Rev-talk] [Revactor-talk] Trouble installing Revactor for Ruby 1.9.1 In-Reply-To: References: Message-ID: On Tue, Nov 4, 2008 at 4:47 PM, Brian Palmer wrote: > I was able to fix this error (in Rev) by changing RB_UBF_DFL to RUBY_UBF_IO > on that line. After that change the latest revision of Rev pulled from > github builds and runs find on Ruby 1.9.1. > Okay, I'll incorporate those changes into Rev. The next release of Rev should build on Ruby 1.8.6, 1.8.7, 1.9.0, and 1.9.1 -- Tony Arcieri medioh.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rogerpack2005 at gmail.com Thu Nov 6 14:24:52 2008 From: rogerpack2005 at gmail.com (Roger Pack) Date: Thu, 6 Nov 2008 12:24:52 -0700 Subject: [Rev-talk] latest on windows mingw... Message-ID: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> Here's the latest output for the record: gcc -I. -I. -Ic:/Ruby18/lib/ruby/1.8/i386-mingw32 -I. -DRUBY_VERSION_CODE=186 -DHAVE_OPENSSL_SSL_H -DHAVE_OPENSSL_SSL_H -g -O2 -c rev_buffer.c rev_buffer.c:630:2: warning: no newline at end of file gcc -I. -I. -Ic:/Ruby18/lib/ruby/1.8/i386-mingw32 -I. -DRUBY_VERSION_CODE=186 -DHAVE_OPENSSL_SSL_H -DHAVE_OPENSSL_SSL_H -g -O2 -c rev_ext.c In file included from rev_ext.c:10: ../libev/ev.c: In function `fd_intern': ../libev/ev.c:981: warning: passing arg 3 of `rb_w32_ioctlsocket' from incompatible pointer type In file included from ../libev/ev.c:1191, from rev_ext.c:10: ../libev/ev_select.c: In function `select_poll': ../libev/ev_select.c:137: error: `NFDBITS' undeclared (first use in this function) ../libev/ev_select.c:137: error: (Each undeclared identifier is reported only once ../libev/ev_select.c:137: error: for each function it appears in.) make: *** [rev_ext.o] Error 1 -- Thanks! -=R From tony at medioh.com Thu Nov 6 16:36:18 2008 From: tony at medioh.com (Tony Arcieri) Date: Thu, 6 Nov 2008 14:36:18 -0700 Subject: [Rev-talk] latest on windows mingw... In-Reply-To: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> References: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> Message-ID: On Thu, Nov 6, 2008 at 12:24 PM, Roger Pack wrote: > ../libev/ev_select.c: In function `select_poll': > ../libev/ev_select.c:137: error: `NFDBITS' undeclared (first use in > this function) > ../libev/ev_select.c:137: error: (Each undeclared identifier is > reported only once > ../libev/ev_select.c:137: error: for each function it appears in.) > make: *** [rev_ext.o] Error 1 > Can you try the latest version on github? I just upgraded it to libev 3.48, and 3.42 was supposed to fix at least the NFDBITS error -- Tony Arcieri medioh.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at medioh.com Thu Nov 6 19:38:19 2008 From: tony at medioh.com (Tony Arcieri) Date: Thu, 6 Nov 2008 17:38:19 -0700 Subject: [Rev-talk] latest on windows mingw... In-Reply-To: <966599840811061353r2132c78dlcb3a9405a57be5a0@mail.gmail.com> References: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> <966599840811061353r2132c78dlcb3a9405a57be5a0@mail.gmail.com> Message-ID: On Thu, Nov 6, 2008 at 2:53 PM, Roger Pack wrote: > > Can you try the latest version on github? I just upgraded it to libev > 3.48, > > and 3.42 was supposed to fix at least the NFDBITS error > > > > Nice--it does seem to get farther. Here's the latest: > Okay, that should be fixed now. Try again. -- Tony Arcieri medioh.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rogerpack2005 at gmail.com Sat Nov 15 20:45:47 2008 From: rogerpack2005 at gmail.com (Roger Pack) Date: Sat, 15 Nov 2008 18:45:47 -0700 Subject: [Rev-talk] latest on windows mingw... In-Reply-To: References: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> <966599840811111502t8bd3182w2899cfbe546fc829@mail.gmail.com> <966599840811121046h2e228e25wf4bacee6d39bfcd4@mail.gmail.com> <966599840811130108p1716d623hb25b4131250a6f4e@mail.gmail.com> <966599840811131324v62a53f1cm5dd68ddfb412d94b@mail.gmail.com> Message-ID: <966599840811151745g42958f68m8077d03bebb4e1e7@mail.gmail.com> More news--that branch now implements the 'libev.o' file [and ev_wrap.h] and also a hacky hack to get it to work with 1.9. I am still not sure why but this time ruby was defining a function 'ioctlsocket' within itself [winsock also defines that function in ws2_32] so linking to ruby first then winsock was hurting libev. Go figure. Anyway it works with 1.9 now. Phew :) Note that currently for windows [and probably for linux too] if you pass too many file descriptors or descriptors who are numbered too high, they might not fit within the fd_set and will be silently ignores, so there's still some lurking scariness in there. I wouldn't expect it to cause problems for web servers, but if you using it to outgoing connections...it might not work past a certain number. also as a note, ctrl+c doesn't work with it currently in windows + 1.9 [until you break out of the loop], which is unexpected. Thanks. -=R On Thu, Nov 13, 2008 at 4:01 PM, Tony Arcieri wrote: > On Thu, Nov 13, 2008 at 2:24 PM, Roger Pack wrote: >> >> That's a branch on my fork of the project. I'm not sure exactly how >> to merge it over. >> >> http://bradlyfeeley.com/2008/09/03/update-a-github-fork-from-the-original-repo/ >> might work. > > Yeah I've done a pull from someone else's fork. Cool. If you're stuff's > ready to pull I'll go ahead and do that. > >> >> A couple of refactors might help: including a local "ev_wrap.h" >> instead of ../libev/ev.h" [then you can put windows specific defines >> in it]. Also splitting out the #include part into its own file >> [thus its own .o file] I think might help with the weird macro >> overwritings. Tough to tell. > > Yeah, I can move libev into its own .o file. The preprocessor approach was > just recommended by libev's author, but now it seems to be causing problems. > > Cool, I'll do a pull tonight and get it merged into my branch. > > Thanks, and great news on Windows support. From tony at medioh.com Sun Nov 16 16:28:54 2008 From: tony at medioh.com (Tony Arcieri) Date: Sun, 16 Nov 2008 14:28:54 -0700 Subject: [Rev-talk] latest on windows mingw... In-Reply-To: <966599840811151745g42958f68m8077d03bebb4e1e7@mail.gmail.com> References: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> <966599840811111502t8bd3182w2899cfbe546fc829@mail.gmail.com> <966599840811121046h2e228e25wf4bacee6d39bfcd4@mail.gmail.com> <966599840811130108p1716d623hb25b4131250a6f4e@mail.gmail.com> <966599840811131324v62a53f1cm5dd68ddfb412d94b@mail.gmail.com> <966599840811151745g42958f68m8077d03bebb4e1e7@mail.gmail.com> Message-ID: Cool... I tried to do a pull but couldn't get it to work. Let me try again... On Sat, Nov 15, 2008 at 6:45 PM, Roger Pack wrote: > More news--that branch now implements the 'libev.o' file [and > ev_wrap.h] and also a hacky hack to get it to work with 1.9. I am > still not sure why but this time ruby was defining a function > 'ioctlsocket' within itself [winsock also defines that function in > ws2_32] so linking to ruby first then winsock was hurting libev. > Go figure. > Anyway it works with 1.9 now. Phew :) > > Note that currently for windows [and probably for linux too] if you > pass too many file descriptors or descriptors who are numbered too > high, they might not fit within the fd_set and will be silently > ignores, so there's still some lurking scariness in there. I wouldn't > expect it to cause problems for web servers, but if you using it to > outgoing connections...it might not work past a certain number. > > also as a note, ctrl+c doesn't work with it currently in windows + 1.9 > [until you break out of the loop], which is unexpected. > > Thanks. > -=R > > > On Thu, Nov 13, 2008 at 4:01 PM, Tony Arcieri wrote: > > On Thu, Nov 13, 2008 at 2:24 PM, Roger Pack > wrote: > >> > >> That's a branch on my fork of the project. I'm not sure exactly how > >> to merge it over. > >> > >> > http://bradlyfeeley.com/2008/09/03/update-a-github-fork-from-the-original-repo/ > >> might work. > > > > Yeah I've done a pull from someone else's fork. Cool. If you're stuff's > > ready to pull I'll go ahead and do that. > > > >> > >> A couple of refactors might help: including a local "ev_wrap.h" > >> instead of ../libev/ev.h" [then you can put windows specific defines > >> in it]. Also splitting out the #include part into its own file > >> [thus its own .o file] I think might help with the weird macro > >> overwritings. Tough to tell. > > > > Yeah, I can move libev into its own .o file. The preprocessor approach > was > > just recommended by libev's author, but now it seems to be causing > problems. > > > > Cool, I'll do a pull tonight and get it merged into my branch. > > > > Thanks, and great news on Windows support. > _______________________________________________ > Rev-talk mailing list > Rev-talk at rubyforge.org > http://rubyforge.org/mailman/listinfo/rev-talk > -- Tony Arcieri medioh.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at medioh.com Thu Nov 20 13:36:09 2008 From: tony at medioh.com (Tony Arcieri) Date: Thu, 20 Nov 2008 11:36:09 -0700 Subject: [Rev-talk] latest on windows mingw... In-Reply-To: References: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> <966599840811121046h2e228e25wf4bacee6d39bfcd4@mail.gmail.com> <966599840811130108p1716d623hb25b4131250a6f4e@mail.gmail.com> <966599840811131324v62a53f1cm5dd68ddfb412d94b@mail.gmail.com> <966599840811151745g42958f68m8077d03bebb4e1e7@mail.gmail.com> Message-ID: And there we go... pulled and merged successfully. On Sun, Nov 16, 2008 at 2:28 PM, Tony Arcieri wrote: > Cool... I tried to do a pull but couldn't get it to work. Let me try > again... > > > On Sat, Nov 15, 2008 at 6:45 PM, Roger Pack wrote: > >> More news--that branch now implements the 'libev.o' file [and >> ev_wrap.h] and also a hacky hack to get it to work with 1.9. I am >> still not sure why but this time ruby was defining a function >> 'ioctlsocket' within itself [winsock also defines that function in >> ws2_32] so linking to ruby first then winsock was hurting libev. >> Go figure. >> Anyway it works with 1.9 now. Phew :) >> >> Note that currently for windows [and probably for linux too] if you >> pass too many file descriptors or descriptors who are numbered too >> high, they might not fit within the fd_set and will be silently >> ignores, so there's still some lurking scariness in there. I wouldn't >> expect it to cause problems for web servers, but if you using it to >> outgoing connections...it might not work past a certain number. >> >> also as a note, ctrl+c doesn't work with it currently in windows + 1.9 >> [until you break out of the loop], which is unexpected. >> >> Thanks. >> -=R >> >> >> On Thu, Nov 13, 2008 at 4:01 PM, Tony Arcieri wrote: >> > On Thu, Nov 13, 2008 at 2:24 PM, Roger Pack >> wrote: >> >> >> >> That's a branch on my fork of the project. I'm not sure exactly how >> >> to merge it over. >> >> >> >> >> http://bradlyfeeley.com/2008/09/03/update-a-github-fork-from-the-original-repo/ >> >> might work. >> > >> > Yeah I've done a pull from someone else's fork. Cool. If you're >> stuff's >> > ready to pull I'll go ahead and do that. >> > >> >> >> >> A couple of refactors might help: including a local "ev_wrap.h" >> >> instead of ../libev/ev.h" [then you can put windows specific defines >> >> in it]. Also splitting out the #include part into its own file >> >> [thus its own .o file] I think might help with the weird macro >> >> overwritings. Tough to tell. >> > >> > Yeah, I can move libev into its own .o file. The preprocessor approach >> was >> > just recommended by libev's author, but now it seems to be causing >> problems. >> > >> > Cool, I'll do a pull tonight and get it merged into my branch. >> > >> > Thanks, and great news on Windows support. >> _______________________________________________ >> Rev-talk mailing list >> Rev-talk at rubyforge.org >> http://rubyforge.org/mailman/listinfo/rev-talk >> > > > > -- > Tony Arcieri > medioh.com > -- Tony Arcieri medioh.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From tony at medioh.com Thu Nov 20 13:38:48 2008 From: tony at medioh.com (Tony Arcieri) Date: Thu, 20 Nov 2008 11:38:48 -0700 Subject: [Rev-talk] latest on windows mingw... In-Reply-To: References: <966599840811061124k1300c5abid767abccdd058ca5@mail.gmail.com> <966599840811121046h2e228e25wf4bacee6d39bfcd4@mail.gmail.com> <966599840811130108p1716d623hb25b4131250a6f4e@mail.gmail.com> <966599840811131324v62a53f1cm5dd68ddfb412d94b@mail.gmail.com> <966599840811151745g42958f68m8077d03bebb4e1e7@mail.gmail.com> Message-ID: And now it won't compile, whoops... were you wanting me to pull from that other branch? On Thu, Nov 20, 2008 at 11:36 AM, Tony Arcieri wrote: > And there we go... pulled and merged successfully. > > > On Sun, Nov 16, 2008 at 2:28 PM, Tony Arcieri wrote: > >> Cool... I tried to do a pull but couldn't get it to work. Let me try >> again... >> >> >> On Sat, Nov 15, 2008 at 6:45 PM, Roger Pack wrote: >> >>> More news--that branch now implements the 'libev.o' file [and >>> ev_wrap.h] and also a hacky hack to get it to work with 1.9. I am >>> still not sure why but this time ruby was defining a function >>> 'ioctlsocket' within itself [winsock also defines that function in >>> ws2_32] so linking to ruby first then winsock was hurting libev. >>> Go figure. >>> Anyway it works with 1.9 now. Phew :) >>> >>> Note that currently for windows [and probably for linux too] if you >>> pass too many file descriptors or descriptors who are numbered too >>> high, they might not fit within the fd_set and will be silently >>> ignores, so there's still some lurking scariness in there. I wouldn't >>> expect it to cause problems for web servers, but if you using it to >>> outgoing connections...it might not work past a certain number. >>> >>> also as a note, ctrl+c doesn't work with it currently in windows + 1.9 >>> [until you break out of the loop], which is unexpected. >>> >>> Thanks. >>> -=R >>> >>> >>> On Thu, Nov 13, 2008 at 4:01 PM, Tony Arcieri wrote: >>> > On Thu, Nov 13, 2008 at 2:24 PM, Roger Pack >>> wrote: >>> >> >>> >> That's a branch on my fork of the project. I'm not sure exactly how >>> >> to merge it over. >>> >> >>> >> >>> http://bradlyfeeley.com/2008/09/03/update-a-github-fork-from-the-original-repo/ >>> >> might work. >>> > >>> > Yeah I've done a pull from someone else's fork. Cool. If you're >>> stuff's >>> > ready to pull I'll go ahead and do that. >>> > >>> >> >>> >> A couple of refactors might help: including a local "ev_wrap.h" >>> >> instead of ../libev/ev.h" [then you can put windows specific defines >>> >> in it]. Also splitting out the #include part into its own file >>> >> [thus its own .o file] I think might help with the weird macro >>> >> overwritings. Tough to tell. >>> > >>> > Yeah, I can move libev into its own .o file. The preprocessor approach >>> was >>> > just recommended by libev's author, but now it seems to be causing >>> problems. >>> > >>> > Cool, I'll do a pull tonight and get it merged into my branch. >>> > >>> > Thanks, and great news on Windows support. >>> _______________________________________________ >>> Rev-talk mailing list >>> Rev-talk at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/rev-talk >>> >> >> >> >> -- >> Tony Arcieri >> medioh.com >> > > > > -- > Tony Arcieri > medioh.com > -- Tony Arcieri medioh.com -------------- next part -------------- An HTML attachment was scrubbed... URL: