You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suppose that a developer want to bind a property that will be used by all callbacks which exist in AJAXRequest instance. Currently, the only why to bind them is by looping throgh all existing callbacks using thier IDs in addition to all pools. The code that the developer will have to write is lengthy.
A suggested solution for this problem is to have a method with following signature: AJAXRequest.bind(name, varToBind [,callbackId [, poolName]])
The method should accept two parameters at least, the first parameter is the name that will be used to access the property and the second one is the value that will be linked. An optional parameter could be a callback ID. So that the binding will only be for the callback with the given ID. A fourth optional parameter could be pool name. So that the variable will be only linked with callbacks in the specified pool.
Suppose that a developer want to bind a property that will be used by all callbacks which exist in
AJAXRequest
instance. Currently, the only why to bind them is by looping throgh all existing callbacks using thier IDs in addition to all pools. The code that the developer will have to write is lengthy.A suggested solution for this problem is to have a method with following signature:
AJAXRequest.bind(name, varToBind [,callbackId [, poolName]])
The method should accept two parameters at least, the first parameter is the name that will be used to access the property and the second one is the value that will be linked. An optional parameter could be a callback ID. So that the binding will only be for the callback with the given ID. A fourth optional parameter could be pool name. So that the variable will be only linked with callbacks in the specified pool.
Associated Tasks:
AJAXRequest.bind(obj [,callbackId [, poolName]])
#19The text was updated successfully, but these errors were encountered: