In that case, it would be a bug. I am looking into it, in the meanwhile please file a bug report.
On Wed, Jan 7, 2009 at 9:37 PM, Jonathan Donaldson <[email protected]> wrote: > I am using memcache, with my backgroundrb.yml set like: > --- > :backgroundrb: > :port: 11006 > :ip: 127.0.0.1 > :result_storage: memcache > :memcache: "127.0.0.1:11211" > Is there something I need to do in the worker to get it to use it? I see the > same behavior with both... > > On Jan 7, 2009, at 11:02 AM, hemant wrote: > > On Wed, Jan 7, 2009 at 9:15 PM, Jonathan Donaldson <[email protected]> > wrote: > > Sorry if this hit twice, my mailer was using the .com version of my email > > address not the .net one I signed up with: > > > Using Backgroundrb pulled from github yesterday, and rails 2.2.2. > > In my worker, I send lots of progress back as I step through the tasks, ie: > > @items.each do |itm| > > ...stuff happens here > > @results[:created_items] += 1 > > cache[some_key] = @results > > end > > in next loop: > > @ results[:errors] = "Error on Item 4", > > cache[some_key] = @results > > when I call ask_result on the worker, I get nil back until after the worker > > is completely done, then I get my results.... > > ideas? This is to drive a progress bar and other 'realtime' feedback... > > You will have to use Memcache based backend of result storage for > "realtime" feedback. Inbuilt cache behavior is like what you > mentioned. > For more info: > > http://backgroundrb.rubyforge.org/workers/#result_caching > > > > > Thanks! > Jonathan Donaldson > Partner, Column3 LLC. > [email protected] > > > > -- Let them talk of their oriental summer climes of everlasting conservatories; give me the privilege of making my own summer with my own coals. http://gnufied.org _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
