search

KanikaVarma / sudzc

Automatically exported from code.google.com/p/sudzc
0 stars 0 forks source link

Architecture issue - there should be a way to know which SoapRequest is calling my handler #52

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Generate code for a webservice
2. Call a method, passing self and a handler for the target and action
3. Notice that all that is passed to the handler is the result.
4. Wish that you knew which SoapRequest this went with.

What is the expected output? What do you see instead?
In an async environment, it's frequently important to know what operation a 
callback belongs to. A good example is NSURLConnection - all of its callbacks 
have the NSURLConnection object passed in as the first parameter.
I would much rather have delegate protocol similar to NSURLConnection's.

What version of the product are you using? On what operating system?
Latest. Lion.

Please provide any additional information below.

Original issue reported on code.google.com by glen.sim...@gmail.com on 20 Jun 2012 at 3:43