Hello All,
Thanks for your input on the RemoteObject topic - I think I have it
working better now.
Now if I keep my RemoteObject in my Application Root, and call it from
my other containers (in this case, a Popup Title Window), how can I
force my "Results" to be returned to that Object? Additionally, if I
create other Containers in the future, I'd like to control where the
Results from the Remoting Call are sent.
BUT, this is my understanding: When defining the Methods within the
RemoteObject declaration, you have to specify the "onResult" and
"onError" functions. How can I control, during program execution, where
those Results are sent - if I choose to send them elsewhere?
I know that I can set a Variable equal to a function name - and then
have in my function residing in the root, a "Return" command, which then
sends the results of the function, to the Calling Component.
But, typically, there are 2 or more functions involved in making a
Remoting Request - #1, the function that calls the Remoting Request, and
then #2, the function that is executed, when the Returning Results come
back from the server.
What is the best way to encapsulate my Remoting Objects, and their
associated Methods, in the Application Root, so that the RemoteObject
can be called from anywhere in the application, and also have those
Results sent to the Calling Component?
Thanks for your advice,
Mike
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
