*hugs Davud and the retarded webmailer configuration with the typo in the
name*
On Mo, 6.08.2007, 09:48, Davud Zülke wrote:
> Nooooo he was quicker :/
>
> Should point out though that I believe a 404 response header is the better
> choice. You could send a Location: header along, but I guess
> XMLHttpRequest will follow those, which ruins the nice idea entirely.
>
> David
>
>
>
> P.S: sitting in the very cool Cluj, Romania, but behind an uncool firewall
> that only allows 80 and 443. So no IRC this week until the sysops here
> give up or my sysops back home make me an SSH tunnel listening on port 80
> xD
>
>
> On Mo, 6.08.2007, 09:39, Ross Lawley wrote:
>> Hi Whisller,
>>
>> It really isn't any different to html requests, they just need to be
>> handled accordingly. I cope with them by adding executeAjax methods
>> to my 404, Disabled, Secure and Unavaliable views and for my Login
>> View.
>>
>> I pass JSON header information back which my default Ajax Handler
>> looks at. All my Ajax requests are unobtrusive, which simplifies
>> thing for me. So for a 404 I send back the following JSON Headers:
>>
>> { 'status' => 'redirect', 'url' => $url} My Ajax Handler class
>> inspects the response and actions accordingly - it does a rediect to
>> the 404 page.
>>
>> A similar approach should solve the problems your having, have an
>> execute ajax / json method for the views and then check the response
>>
>> _______________________________________________
>> users mailing list
>> [email protected]
>> http://lists.agavi.org/mailman/listinfo/users
>>
>>
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.agavi.org/mailman/listinfo/users
>
>
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users
