So it appears after a bit of reading the best method of dealing with
this problem, isn''t to deal with it directly.
It seems that providing feedback to the user (cursor into a wait state
or a showing a spinner) that something is happening is sufficient stop
them from doing other actions until it is completed. This seems rather
haphazard to me. For certain operations its fine, say when you''re
simply updating another pane with information, but becuase this is
actually updating the database and can cause the database to not
reflect what the user observes it doesn''t strike me a very good
solution at all.
Does anyone care to comment on this? Is a synchronous ajax request the
best way to go even though it locks the browser?
Thanks
--
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.