Ok. So I upgraded to the git version of backgroundrb and now experience the same results on mac 10.5.3 and debian. The problem is that ask_result doesn't seem to work at all. Hemant, is the move towards using memcached for passing results/status queries a sign that native ruby handling of that will be (is?) deprecated?
-pbaker On 7/31/08, hemant <[EMAIL PROTECTED]> wrote: > > On Thu, Jul 31, 2008 at 6:26 PM, P Baker <[EMAIL PROTECTED]> wrote: > > Granted there is inherent scalability problems in Ruby. I'm not really > > planning on storing more than status markers in the cache. I'm so > reluctant > > to implement memcached on our stack because I don't see the need for it > at > > this point. I can see the argument for large scale websites and the need > to > > pass such large numbers of objects, but I don't think I fit into either > of > > those categories. > > > > I've read your hints on debugging backgroundrb, which suggested running > the > > git version, although I'm also looking for stability. What is the > stability > > like of the master git branch? Since that requires the git version of > > packet, what's the stability of 'edge' packet? > > > For running git version of backgroundrb you don't need git version of > packet. Latest gem will do. >
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
