<div dir="ltr">I think this is an interesting proposal, and I'm not opposed to including more type safe json, but as of now, community solutions are perfectly fine and I'd rather see us focus on getting the basic building blocks first before moving on to more of the "nice to haves" like JSON here.<br><br>Not sure how others feel about it, but that's where I'm landing.<div><br></div><div>- Logan</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 2, 2017 at 11:49 AM Helge Heß via swift-server-dev <<a href="mailto:swift-server-dev@swift.org">swift-server-dev@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class="gmail_msg">
<br class="gmail_msg">
I think it should probably replace JSON deserialisation stuff, maybe the whole plist stuff, in Foundation. IMO it is common enough to actually live in Foundation.<br class="gmail_msg">
<br class="gmail_msg">
Do we need a Swift Extended Library? I’m pretty sure we don’t. There are plenty of ‘Swift Extended Libraries’ already and users can pick the ones they like just fine. Isn’t Zewo supposed to be such a "community supported package”?<br class="gmail_msg">
<br class="gmail_msg">
If your concern is Foundation bloat, I think the solution to this is splitting Foundation into individual submodules (like Foundation.io, Foundation.http, Foundation.json, Foundation.security, etc).<br class="gmail_msg">
Everything which should be ‘standard Swift’ and applies to both client&server should just live in Foundation. IMO.<br class="gmail_msg">
<br class="gmail_msg">
hh<br class="gmail_msg">
<br class="gmail_msg">
P.S.: I’d hope that such a JSON library will properly support push-parsing/streaming, both when constructing JSON types (feed from NIO byte stream) as well as during generation of JSON (say when you fetch objects from a DB and then deliver them to a JSON client, you wouldn’t want to fetch all objects into memory to be able to generate JSON from them in a ’type-safe’ way). I don’t think this is particularly hard, but it needs to be considered, especially if the API would be sealed.<br class="gmail_msg">
<br class="gmail_msg">
> On 2 Mar 2017, at 09:27, Swizzlr via swift-server-dev <<a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> Tl;dr: I believe Swift's core libraries should include typesafe JSON handling.<br class="gmail_msg">
><br class="gmail_msg">
> Preamble: Foundation's JSON serialisation is remarkably (and known to be) finicky, since it's mostly looking NS* objects. While this is a bug that could be rectified, the recursive JSON enum pattern has proven quite popular in recent months and I think something of this sort should be added to support typesafe JSON (de)structuring. This is a separate concern to writing a UTF-8 string; we already have parsers and writers in Swift that are pretty good.<br class="gmail_msg">
><br class="gmail_msg">
> API design: we can go over this in a swift evolution proposal, we need to address another problem first:<br class="gmail_msg">
><br class="gmail_msg">
> Where do we put it?!:<br class="gmail_msg">
><br class="gmail_msg">
> The standard library is probably not the right place for a JSON type. With that out of the way, the Foundation library is overly constrained by its portability requirement with the unfortunately closed source implementation of Foundation on Apple platforms.<br class="gmail_msg">
><br class="gmail_msg">
> Do we need a Swift Extended Library? Perhaps as a community supported package?<br class="gmail_msg">
><br class="gmail_msg">
> Eager to hear the thoughts of all on this list.<br class="gmail_msg">
><br class="gmail_msg">
> Tom<br class="gmail_msg">
><br class="gmail_msg">
> Sent from my iPhone<br class="gmail_msg">
> _______________________________________________<br class="gmail_msg">
> swift-server-dev mailing list<br class="gmail_msg">
> <a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a><br class="gmail_msg">
> <a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-server-dev</a><br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-server-dev mailing list<br class="gmail_msg">
<a href="mailto:swift-server-dev@swift.org" class="gmail_msg" target="_blank">swift-server-dev@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-server-dev" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-server-dev</a><br class="gmail_msg">
</blockquote></div>