Re: efficient ajax calls using flash?

Jason Norris
2006-10-19T20:41:11Z

1.) Neither Flash nor Session are stored on the client machine. They are all
on the server.

2.) By default, rails stores session information on the filesystem. This is
fine, unless you need to share sessions across servers in which case you can
have Rails store session data in the database. It''s easy if you want to
go
that route. Google it.

3.) Yes, running a one-item query by ID is the easiest thing a DB server can
do. Unless you want to do :select => ''SQL_CACHE *'' which
will do a cached
query, thus increasing database speed as much as humanly possible.

Jason

On 10/19/06, Eric Gross
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:
>
>
> What do you mean using the database as the session store? On this note,
> is there any advantage to using flash with flash.keep across actions as
> opposed to session? Is it less "resource intensive" or bulky to
use
> flash or does it not matter since its both stored on the clients
> machine.
>
> So Jason, what I understand from your response is that by storing the ID
> and requerying that specific entry from the database using find is
> really negligable as far as taking up database querying resources?
>
>
> Jason Norris wrote:
> > The other option would be to store it in the session(not the flash -
> > that doesn''t stick around between requests), but if
you''re using the
> > database as the session store, then it''s the same thing. You
Could also
> > insert the ID or whatever you need to store into the AJAX params, that
> > way it would be "stored" in the HTML on the client machine.
>
>
> --
> Posted via http://www.ruby-forum.com/.
>
> >