Unsupported Classes

[johnezang]

Unsupported Classes

[soffes]

I love that idea. I think it would be neat if it was something like

- (id)JSONValue;

That just returned one of the supported classes, since most of the time you would want to return a dictionary or an array or something.

[a2]

How about something like:

@protocol JKCoding <NSObject>

- (id) JSONRepresentation;
- (id) initWithJSONRepresentation: (id);

@end

Remember that if we implement something like this, the JSON will just contain an array, dictionary, string, or number representation of this object. What we need to do is somehow store the class hierarchy "chain" like Apple does in its .plists so that we know what class we have when we're unarchiving/unserializing. The reason we store the class hierarchy is so that if the first class is unavailable we can default to the next, and so on.

Perhaps something like:

If MyArray is an NSMutableArray subclass, and -[MyArray JSONRepresentation] yields @"JSON VALUE", we could encode it like this:

["JSON_VALUE", "MyArray", "NSMutableArray", "NSArray", "NSObject"].

[johnezang]

Is there any reason why the current block / delegate pattern in place can't be used to implement this?

I don't necessarily disagree with the request. It's more a matter of finding the balance between which features should be included in the core and providing primitives that allows the end-user to easily extend the core to better fit their particular needs.

I'm of the opinion that it's far more important to provide high quality general purpose primitives that would allow a feature like this to be implemented than necessarily providing the feature itself. What's a must have feature to use is bloat to someone else. :) I think something like this would be better done in a Cookbook.md like file that would provide patterns that others would likely find useful while at the same time serving as documentation on how to make use of the provided primitives to accomplish something.

Thoughts?

[a2]

No, you're right. You have to develop for 80% of your target user base. The feature I'm describing would be for encoding entire objects, which is something that could go in a Cookbook file.

Cheers

[teerapap]

I agree that block/delegate pattern is useful enough. However, in case there are many objects of unsupported classes, there would have many temporary NSDictionary or NSArray objects along the serialization.

Is there a way to deal with this situation?

How about an selector of the delegate that serialize the object by itself to a buffer or NSMutableData which JSONKit provided.