Jeremy,

Thanks for your quick response. You're right that I didn't dig into the documentation, but I see now how the GSearch interface works, and it is exactly what I needed. Thanks for pointing me in the right direction.

One thing I noticed, though, is that the callback specified by the setSearchCompleteCallback method is not called according to the specification in the documentation. Instead of receiving the search object as an argument, in my experiments, it was passed a single null argument. I am able to work around this by keeping a reference to the original search object.

Also, on the topic of callbacks, although I appreciate the effort of this specification to solve the "scope" problem, the method chosen here is not an ideal solution. Any developer who writes object- oriented Javascript necessarily has an existing solution to this problem that works for them and their team. I don't think its fair to suggest developers do the same thing in two different ways just because your method signature makes it a little easier.

If you would like to supply an interface to help the casual and professional programmer simultaneously, I recommend changing the method signatures from (object, method) to (method, object). That way, I can still pass in my scope-bound methods that I use everywhere else in my code, and I don't need to pollute the call with an unused parameter.

On May 28, 6:41 pm, "jgeerdes [AJAX APIs \"Guru\"]" <jgee...@mchsi.com> wrote: