Note that there are some explanatory texts on larger screens.

plurals
  1. USDaniel Crenna
    primarykey
    data
    text
    plurals
    1. COThe point is that the UINavigationBar in the base class is not settable. The standard approach in iOS is to subclass, use categories, or invoke the ObjC runtime to swap the implementation at runtime. There is no way to pass anything "down to the base class". And the custom code (not in this example) does draw; just not additional navigation items. Clearly I need a way to hook up my implementation earlier in execution, but it does not appear to exist.
      singulars
    2. COAlso, check this out re: indempotence - http://stackoverflow.com/questions/741192/whats-the-correct-way-to-view-idempotency-in-terms-of-http-delete ... I won't spend too much time defending GET here, since why not use POST and avoid the possibility of human error, but it isn't as evil as most people claim.
      singulars
    3. COI understand idempotence, like you mentioned, but GET and DELETE other than that specification detail, are identical. DELETE should also be idempotent. People sometimes get confused by the difference between idempotence and not changing state. What I mean is the first GET could delete the entity, the next GET to the same URL should return 404 or similar. That's why I said protect your GET with authorization. Same thing applies with DELETE. I see no real argument here to prefer POST over GET if GET is protected from web crawling. A DELETE is URL-based as well, so it can be "corrupted" as well.
      singulars
 

Querying!

 
Guidance

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