Please help with writing spec for async JSON APIs

[Kevin Smith]

Hi Moshen,

The semantics of your proposal are straightforward, so I don't think you
need to provide spec text at this point.  Instead, what would be helpful is
a quantitative analysis showing why these additional methods are needed.
Is there any way you can demonstrate the benefit with numbers?


On Fri, Jul 31, 2015 at 11:04 PM Mohsen Azimi <me at azimi.me> wrote:

> Hi,
>
> I stumbled on lack of async APIs for JSON parsing and stringifying in
> JavaScript a couple of weeks ago. I tried to hack
> <http://azimi.me/2015/07/30/non-blocking-async-json-parse.html> around it
> by abusing the W3C Fetch API but that's just a hack.
>
> Domenic suggested <https://twitter.com/domenic/status/626958415181393920>
> that we should write the proposal spec for native non-blocking JSON
> processing. I don't know what the API should look like but I made some
> assumptions and wrote the initial spec (if I can call it spec!) and
> published it in GitHub <https://github.com/mohsen1/async-json>.
>
> I need to learn the spec lingo and rewrite the spec in proper and standard
> language. I need help and resources to learn the language of the spec.
>
> Would you please review the proposal so far (including the outstanding PR)?
>
> Thanks,
> Mohsen
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150801/d8894db8/attachment.html>