Backgroundrb devel - Oct 2007 - Need advice - which version to use?

Greetings!

I could use some advice on which version of BackgrounDrb to use in my current
situation.  I''ve implemented the initial, single-process multi-threaded
version in a previous site, but have no experience with the new version. 
Current situation is as follows.

The application involves personal health information and so has very stringent
session management requirements.  My question derives from the need to reset the
session (to require re-login) when the visitor closes their browser.  Current
thought-process is to use periodically_call_remote to set a session variable
that can be checked by a worker to determine whether or not the browser is still
there.

Anybody got any thoughts to share on the pros and cons of either version of
BackgrounDrb for this?

Thanks in advance,
Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20071024/882285fb/attachment.html

On 10/24/07, Bill Walton <bill.walton at charter.net>
wrote:
>
>
> Greetings!
>
> I could use some advice on which version of BackgrounDrb to use in my
> current situation.  I''ve implemented the initial, single-process
> multi-threaded version in a previous site, but have no experience with the
> new version.  Current situation is as follows.
>
> The application involves personal health information and so has very
> stringent session management requirements.  My question derives from the
> need to reset the session (to require re-login) when the visitor closes
> their browser.  Current thought-process is to use periodically_call_remote
> to set a session variable that can be checked by a worker to determine
> whether or not the browser is still there.
>
> Anybody got any thoughts to share on the pros and cons of either version of
> BackgrounDrb for this?
>
Although you can try the trunk version of BackgroundDrb, which works
most of the time. I will be putting a new version of BackgroundDrb up
on this weekend, so watchout.

-- 
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

Hi hemant,

hemant wrote:

> On 10/24/07, Bill Walton <bill.walton at charter.net> wrote:
> >
> > Anybody got any thoughts to share on the pros and cons of either
version
of
> > BackgrounDrb for this?
> >
>
> Although you can try the trunk version of BackgroundDrb, which works
> most of the time. I will be putting a new version of BackgroundDrb up
> on this weekend, so watchout.
>
I should have mentioned another component of the decision I''m facing
....

Our current deployment is ruby / mongrel cluster but we hope / plan to move
to JRuby / JBoss in the near future.  (That was our initial rollout but
experience showed that our infrastructure team wasn''t staffed / tooled
to
support it, so we had to roll back to our current deployment).

I just had an IRC chat with Skaar on the jruby channel and he says trunk
won''t work with jruby.  He says the old version might, and he says that
your
upcoming implementation might be even better suited to jruby.  My needs for
BackgrounDrb are pretty simple at this point:  just periodically checking a
session variable to see if it''s been updated.  I need to do my best to
make
sure that whatever I do on this front doesn''t have a negative impact on
our
move to JRuby.  Would definitely appreciate any thoughts you''d be
willing to
share on this front.

Thanks,
Bill

On 10/24/07, Bill Walton <bill.walton at charter.net>
wrote:
> Hi hemant,
>
> hemant wrote:
>
>
> > On 10/24/07, Bill Walton <bill.walton at charter.net> wrote:
> > >
> > > Anybody got any thoughts to share on the pros and cons of either
version
> of
> > > BackgrounDrb for this?
> > >
> >
> > Although you can try the trunk version of BackgroundDrb, which works
> > most of the time. I will be putting a new version of BackgroundDrb up
> > on this weekend, so watchout.
> >
>
> I should have mentioned another component of the decision I''m
facing ....
>
> Our current deployment is ruby / mongrel cluster but we hope / plan to move
> to JRuby / JBoss in the near future.  (That was our initial rollout but
> experience showed that our infrastructure team wasn''t staffed /
tooled to
> support it, so we had to roll back to our current deployment).
>
> I just had an IRC chat with Skaar on the jruby channel and he says trunk
> won''t work with jruby.  He says the old version might, and he says
that your
> upcoming implementation might be even better suited to jruby.  My needs for
> BackgrounDrb are pretty simple at this point:  just periodically checking a
> session variable to see if it''s been updated.  I need to do my
best to make
> sure that whatever I do on this front doesn''t have a negative
impact on our
> move to JRuby.  Would definitely appreciate any thoughts you''d be
willing to
> share on this front.
>
Do you need to trigger this check from rails? If yes ( as i think, you
want this), then please evaluate trunk of backgroundrb. It should
work.

As for Jruby compatibility, I can''t comment on that, I currently have
little plans of porting it to jruby.


-- 
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

hemant wrote:
>
> Do you need to trigger this check from rails? If yes ( as i think, you
> want this), then please evaluate trunk of backgroundrb. It should
> work.
I''m not an infrastructure-type guy.  Don''t know much at all
about the issues
/ implications of single-process/multi-threaded vs.
multi-process/single-threaded choice the two versions of BackgrounDrb put in
front of me.  I sure could use some advice on the pros / cons of each.

Our current environment is 4 app servers (dual processor, 4GB) with each
running Rails and a 60-mongrel cluster, hardware loadbalancers in front
them, Apache / HAproxy in front of the mongrels.  All 4 talk to a MySQL
cluster running on separate hardware.  Session store is ActiveRecord.

Any thoughts re: pros/cons of the two architectures would really be
appreciated.
>
> As for Jruby compatibility, I can''t comment on that, I currently
have
> little plans of porting it to jruby.
>
Skaar''s comment was that trunk will definitely not work on JRuby. 
Slave
will have to be re-written.  He said that the old version might work.  I
haven''t tested it yet.  In either event, if we (the company I work for)
need
to make mods to use either version of BackgrounDrb on JRuby in the future,
I''m pretty sure we''ll be able / willing to contribute it back.

Looking forward to hearing your thoughts.

Thanks,
Bill