Hmm, I think it checks for the crossdomain.xml file when the webservice
attempts to load/connect. Simple access to a file on a remote (sub)domain is
not allowed.
On 6/20/07, jason vancleave [EMAIL PROTECTED] wrote:
Seth Green seth.m.green at gmail.com writes:
It turns out that the
I suspect the first call delay is to do with flash getting a wsdl file (if
its a SOAP service). Once it has the wsdl, it needs not d/load it again.
On 6/21/07, elibol [EMAIL PROTECTED] wrote:
Hmm, I think it checks for the crossdomain.xml file when the webservice
attempts to load/connect.
yeah, that may very well be it.
jtgxbass wrote:
I suspect the first call delay is to do with flash getting a wsdl file (if
its a SOAP service). Once it has the wsdl, it needs not d/load it again.
On 6/21/07, elibol [EMAIL PROTECTED] wrote:
Hmm, I think it checks for the crossdomain.xml file
Maybe I am misunderstanding something bu I would think you could set up a
methodology where JS makes a call to Flash, Flash returns something immediately
to JS, then does its stuff with the web service and calls back to JS again when
its done.
Another option is instead of using
I can try that, but since flash isn't multithreaded, I'm not sure that
would work. You mean if I had in AS
function calledFromJS():Void {
doSomething();
return;
}
right? I believe the call to that function would still take as long as
doSomething() takes. Unless I misunderstood...
jason
Seth Green seth.m.green at gmail.com writes:
It turns out that the asynchronous web service call actually takes
some extra time (like 100ms) the FIRST time you use that web service
method.
Not to confuse the matters worse but I wonder if that has something to do with
it looking for the a
6 matches
Mail list logo
