Hi Ben, As of my impression, the best way to use it is to organize so called "gracefull degradation", i.e., to manage sutuations, when a user has JS in his/her browser off.
Clearly, any "ajaxian" web app must consider such a situation explicitly; if the request is "ajaxian", prototype.js sends the corresponding header, thus, Request.is_xhr is True (request.xhr? in case of Rails) and server can safely send the response, e.g., in the JSON format; if that header is absent, Request.is_xhr returns False and sending the JSON data becomes risky. I suppose, this is a common task, once one will have to check the availability of javascript on the client side every time and then. In any case, inclusion of the is_xhr method will not produce any problem: if a developer doesn't need it, (s)he simply is not going to use "is_xhr'. Greetings, Giorgi Ben Bangert wrote: > What does usage of the attribute look like? I'm open to including it in > Pylons request object. > > Cheers, > Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss -~----------~----~----~----~------~----~------~--~---
