Hello Jim, We had the same problem when we upgraded Backgroundrb. The solution provided by hemant was to add these line in your backgroundrb.yml config
:backgroundrb: :result_storage: memcache :memcache: "127.0.0.1:11211" With that in place, ask_worker should start working. Regards Kieran On Fri, Nov 7, 2008 at 5:13 AM, Jim Nicholson <[EMAIL PROTECTED]>wrote: > We've used previous versions of backgroundrb to handle long-running > tasks, like ingesting large XML uploads into the database. In the > previous API, we could set accessors on workers and use them to provide > status and progress indicators as the main worker method churned away. > > With the recent API changes, I can't see how this sort of thing would be > done. It seems that calls to "ask_results" while a method is running > always return nil, rather than whatever the current contents of the > cache are. > > Is there some mechanism I'm missing for doing this sort of thing? I can > see the usefulness of the new API and support for clustering, etc, but > if I can't give the user feedback on an active worker's progress, I'm > going to have to go back to the previous incarnation of backgroundrb. > > > > _______________________________________________ > Backgroundrb-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/backgroundrb-devel >
_______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
