I thought the explination was a simple one.

To recap....

A global way of knowing what is going on inside Ajax requests including.

1. The element that triggered the call
2. The container (if Ajax.Updater) the response is going to.

Yes i have looked at Responders and i am using them now to lock (disable) 
input elements but as i cannot get the element that triggered the call i 
have to lock the whole document which is not neccesary and slow - it would 
be better to find the parent or inputs above the callee and lock them while 
the request is going on (to stop people pushing the button twice etc etc) 
then unlock on onComplete.

My way is working fine at the moment ... but ... it would be quicker and 
more efficient if i could in some way get the nodes/elements i desire on a 
global basis as part fo the framework and not hacked ontop of it.

Hope this clears things up a bit

Alex Mcauley
----- Original Message ----- 
From: "Timo" <>
To: "Prototype &" <>
Sent: Tuesday, August 25, 2009 4:11 PM
Subject: [Proto-Scripty] Re: Ajax requests again

> On 20 Aug., 17:15, Alex Mcauley <>
> wrote:
>> earlier on in the month i posted on how to do some things with Ajax
>> requests genericaly like adding a loading message to all requests and
>> i got a couple of responses but not many.
>> I've been giving it alot of thought and i cam up with addMethods as a
>> way to add some things to the Ajax Class...
>> Could anyone give me an example of how to do this with addMethods -
>> just a hello world will do then i can take it from there
> I am not sure I understand what you are trying to achieve (and I
> couldn't find the older topic you mention),
> but did you look at Ajax.Responders? [
> ajax/responders]
> Timo
> >

You received this message because you are subscribed to the Google Groups 
"Prototype &" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to