08-13-2011 07:21 AM
08-13-2011 07:29 AM
The work around that hifetz refered works fine. But my question is what is the point in writing different methods to invoke a functionality it if both behaves exactly the same -- transport.makeSyncCall and transport.makeAsyncCall
08-15-2011 08:38 AM
Hi praveen_rajan ,
The thing of it is this, often we make asynchronous calls down into the system, but we don't do it in the expected manner. We do a synchronous call down sending the information and let the system call back when it feels like (this allows patterns like listeners). Anywhere you see transport.makeAsyncCall is just a code error on our part.
08-15-2011 08:42 AM
08-15-2011 01:56 PM - edited 08-15-2011 02:22 PM
There is no transport.makeAsyncCall anywhere in ext. Do you mean *.makeAsyncCall?
EDIT: I went through the code and transport objects are created, so they have different names (remote, request, etc.). Changing the calls on those objects to the sync version fixed the problem.