Jaikishan, There's no such thing in HTTP. The server can only answer client requests, not the other way around.
Your 1st approach is correct, except your assumption of needing a separate thread. What Fred meant is that exactly that, you don't need a separate thread. Your regular Rails app should be more than capable to respond to these AJAX requests. Cheers, Sazima On Dec 11, 7:28 am, "Jaikishan Jalan" <[EMAIL PROTECTED]> wrote: > Solving the similar problem, I am not sure if my previous approach was the > right way. Another thing I could think of is that my server keeps sending > data to my client side proactively for every 5 seconds. How that can be > acheived in rails? > > On Thu, Dec 11, 2008 at 2:30 PM, Frederick Cheung < > > > > [EMAIL PROTECTED]> wrote: > > > On 11 Dec 2008, at 02:53, Jaikishan Jalan wrote: > > > > However, as I understand that this thing needs to be implemented as > > > a separate thread so that rest of the components on the webpage > > > remains interactable. > > > That's not true. > > > Fred > > > > Is this the right approach to solve this or is there a better way to > > > do it? > > > > -- > > > Thanks, > > > Jaikishan > > -- > Thanks, > Jaikishan --~--~---------~--~----~------------~-------~--~----~ 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@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
