MKNetworkOperation postDataEncoding Content-Type headers are set in initWithURLString about mknetworkkit HOT 6 CLOSED

I'm still thinking of a good architecture for this, without adding a parameter.
For example, setting it in the Engine subclass and all operations created on the Engine uses the same encoding.

from mknetworkkit.

So, if you wanted to do different requests with different content types, you'd use different engines?

from mknetworkkit.

MKNetworkEngine should be subclassed for every different server you connect to from your app.
How often would you have a server that uses different content type encoding for different end points?
Does that make sense or am I over assuming?

from mknetworkkit.

Um, in my case I have a server that has different content type... but I can just use different engines for each type, it'd be a simpler api.

from mknetworkkit.

Since current version of initWithURLString contains switch (self.postDataEncoding) and there is no dynamic way to set self.postDataEncoding, it seems like a potential API design issue or that I'm using (something) in wrong way.

Would prefer API extension, but updated docs are fine, too.

In case it makes any difference, I need to post json inside multipart.

from mknetworkkit.

same issue here ... I have one engine, one server, but depending on the method to post to, two different types of content-type to send. An additional helper method might be the only way, unfortunately :/

from mknetworkkit.