|
Yes, this helps a lot. I was trying to
extend HTTPService so I could add some properties, but I think I see that I
should be adding that kind of information to the “event.call” instance.
Analyzing your response lead me to search the docs for event.call, where I
found another good example, plus a link to the “ACT” pattern. I have enough info to keep me busy both
practically and theoretically. Thanks a lot. Tracy From: Matt Chotin
[mailto:[EMAIL PROTECTED] The result that's being specified in the
tag is the handler for the result event, it is not the result property.
The result property is filled in automatically when the service returns. I'm assuming this is based on trying to
solve a problem from your last post which I just answered. I do not
recommend extending HTTPService unless you're really sure it's what you want to
do. Generally the HTTPService is used in conjunction with another class,
and that class can be extended. But unless you're trying to change the
behavior of HTTPService and know what you're doing I think extending isn't
necessary (especially since I didn't document how it actually works
internally). Matt -----Original Message----- When using the mx:HTTPService tag as is, I can set a
result handler. |
