• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Why are properties access through NSURLProtocol class method rather than NSURLRequest instance method?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Why are properties access through NSURLProtocol class method rather than NSURLRequest instance method?


  • Subject: Why are properties access through NSURLProtocol class method rather than NSURLRequest instance method?
  • From: Larry Campbell <email@hidden>
  • Date: Sun, 15 May 2011 22:57:10 -0400

Seems odd to me that setting and getting properties of an NSURLRequest involve an NSURLProtocol class method:

    +[NSURLProtocol setProperty:forKey:inRequest:]

rather than what seems to me the much more straightforward:

    -[NSMutableURLRequest setProperty:forKey:]

Is there a reason for this?

- lc

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Why are properties access through NSURLProtocol class method rather than NSURLRequest instance method?
      • From: Mike Abdullah <email@hidden>
  • Prev by Date: CoreData mapping two different objects to same entity?
  • Next by Date: Re: CoreData mapping two different objects to same entity?
  • Previous by thread: Re: CoreData mapping two different objects to same entity?
  • Next by thread: Re: Why are properties access through NSURLProtocol class method rather than NSURLRequest instance method?
  • Index(es):
    • Date
    • Thread