On Thu, Sep 09, 2010 at 10:20:32AM -0700, I. E. Smith-Heisters wrote: > On Sep 8, 5:08 pm, John Mettraux <[email protected]> wrote: > > > > > Here's the gist with my monkey patches:http://gist.github.com/570681. > > > I thought some portion of them might be suitable for incorporation > > > into mainline. I haven't done extensive testing or field-use of these > > > yet--that will be coming in the next few weeks. I'll keep the gists > > > and the list updated with any significant patches. > > > > I'm very interested to merge your work into the mainline, I'm wondering if > > my pagination (it's for all storages) and your patches could get along. I > > will study carefully your gists. > > I'd be happy to refactor my code to fit into yours. For instance, my > modification to StorageHistory should really be done by subclassing > StorageHistory (perhaps as Ruote::Couch::StorageHistory) so that > Ruote::StorageHistory remains compatible with the usual storage > interfaces. > Unless you intend to add some mechanism for selecting a > special database class (WfidIndexedDatabase) to all storages?
Hello, OK, I will look at that issue in more details. I will work on integrating your work and think of extensibility. > > Feel free to indicate your requirements and point at weaknesses like you > > just did. I hope we can work together to make the whole ruote system > > better, at least for you. > > We also ran into some issues because Ruby's HTTP implementations suck > (eg. > http://apocryph.org/2008/10/04/analysis_ruby_18x_http_client_performance/). > We moved to Patron, which helped significantly, but we're working on a > Memcached cache layer for Ruote::Couch that helps even more. It's not > baked enough for release, but we'll let you know when it is. Of > course, getting Ruby's HTTP up to speed would obviate the need for > this. That's interesting, in my ruote-couche using projects, I moved away from Patron for a testing issue that bothered me, I've probably got way less users than you do, so I was happy with ruby's HTTP. http://github.com/toland/patron/issues#issue/12 (Too bad, this is not even involving ruote-couch). Quick note : ruote-couch uses ruby's HTTP anyway for continuous feeds : http://github.com/jmettraux/rufus-jig/commit/26c78da01d8c5cb4a3ffaf11d11593fd9d27ffec It was way simpler to do it that way than to work it for patron, ruby and em-http-request. Thanks for all the feedback, I will go on with the storage history thing. Cheers, -- John Mettraux - http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
