Thanx for the info, i'll look deeper into the informations rigt after sending this post (i would appreciate if you could post some further informations).
@Tracy By "it didn't seem to work" i meant that the ready property was false after sending a request. By concurrentyl i mean having one Web Service instance which can call multiple operations without canceling the previous and let all calls be managerable (in a sence of be able to differentiate between the single results that come in). Best regards and thanx for the info so far. --- In flexcoders@yahoogroups.com, "app.developer" <[EMAIL PROTECTED]> wrote: > > Look up AsyncToken. This extend the EventDispatcher. > > This class provides a place to set additional or token-level data for > asynchronous RPC operations. It also allows an IResponder to be > attached for an individual call. > > Associate this to the SEND.... > var token:AsyncToken = service.send(Params); > token.addResponder(responder); > > The 'responder' will let your WS know where to return the results. > > I can write a longer answer after EOB. > > PCC > > --- In flexcoders@yahoogroups.com, "florian.salihovic" > <florian.salihovic@> wrote: > > > > I'm currently trying to call with one WebService instance a WebService > > several time concurrently. But it seems like it won't work. Is there a > > way to achieve it? > > > > I'm using an instance of mx.rpc.soap.WebService. > > > > Any help would be appreciated. > > >
