Hello, I would agree with Michael... if only having the node <myns:request><foo>value</foo></myns:request> have not returned a compilation error on "foo is not implemented". But i did not want to implement de "foo" property in my extended rpc.mxml.HTTPService class... any workaround ?
vincent --- In [email protected], "Michael Labriola" <[EMAIL PROTECTED]> wrote: > > Sebi, > > Assuming this is something you have to, or really want to do at this > layer... > > My first thought would be to extend the HttpService class. > > Override the send method. If a current request is not pending, call > super.send( params), else queue it. > > Then add event listeners for both the result and fault events of the > service. When either a result or fault happens, send the next one out > of the queue. > > There might be a more elegant way... but that was my first thought. > > Mike > > --- In [email protected], "Sebastian Feher" <sebif@> > wrote: > > > > I need to limit the number of HTTP connections available to > > mx:HTTPService to 1. As I could not find a way of configuring this I > > plan to write my own component (only for the concurrency=multiple > > scenario) to queue the requests, allow only one connection at a time > to > > pass through and handle the results properly. > > > > My Flex skills are ok and I previously wrote UI Components. Where > > should start from? > > > > Thanks in advance, > > Sebi > > >
