Databases
StackOverflow2013
Postsdbo
POHow should I return an NSError object from a delegate method?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow should I return an NSError object from a delegate method?
    primarykey
    data
    text
    <p>I'm designing a delegate method that is called when the remote server needs input from the delegate. The delegate at that point is responsible for filling in data to be sent to the server and also telling the server if there is an error at that point.</p> <p>The delegate method I have right now is:</p> <pre><code>-(void)server:(MBServer*)server willSendData:(NSMutableString*)data error:(NSError**)error; </code></pre> <p>At this point, the delegate can provide data for the server to send by modifying the NSMutableString that is passed in. Additionally, it can create an NSError to be sent back by setting the <code>error</code> variable to the new NSError instance.</p> <p>The problem I have with this is that the delegate method might be called from another thread via an NSInvocation. The delegate can create a new NSError object, but it will be autoreleased in the current thread before the other thread receives the response.</p> <p>In a single-threaded app, this wouldn't be a problem because the delegator could just retain the response straight away but I can't do that in a multi-threaded design (again because the current event loop will autorelease it). The delegate MUST retain the error so the delegator can release it.</p> <p>This is for a public api and I don't like the idea of requiring via documentation that implementers know they have to retain the error object. It seems too unsafe.</p> <pre><code>// You *must* retain the returned error before // passing it back or you will crash -(void)server:(MBServer*)server willSendData:(NSMutableString*)data error:(NSError**)error; </code></pre> <p>Other ideas I have thought of were to send an NSError as the return value (seems somewhat non-standard as most methods return a bool and take an NSError double-pointer). It also just looks weird.</p> <pre><code>-(NSError *)server:(MBServer*)server willSendData:(NSMutableString*)data; </code></pre> <p>I've also thought of passing a mutable dictionary and asking the delegate to fill in an error. The dictionary would then retain the error, safely getting it back across threads.</p> <pre><code>// Send your NSError response in the dictionary with the key // MBServerErrorResponseKey -(void)server:(MBServer*)server willSendData:(NSMutableString*)data response:(NSMutableDictionary*)response; </code></pre> <p>Has anyone dealt with this design problem and if so what was your solution?</p> <p>Thank you.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMichael Bishop
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow should I return an NSError object from a delegate method?
      1. USjschmidt
      1. VTFavorite
    2. VO
      singulars
      1. POHow should I return an NSError object from a delegate method?
      1. USdigdoritos
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload