[
https://issues.apache.org/jira/browse/AVRO-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975565#comment-14975565
]
Matthieu Monsch commented on AVRO-1747:
---------------------------------------
Thanks! I'll wrap up a few changes in the pipeline and start going through the
steps detailed here -
https://cwiki.apache.org/confluence/display/AVRO/How+To+Contribute. Related to
a point mentioned above, there already is a `js` directory with a
schema/protocol validator; where should the new code live?
Also, one of my goals with `avsc` was to build a library that is simple and
fits in well inside the node.js ecosystem: using built-in streams, buffers,
callbacks where appropriate, etc. Looking at a few other implementations they
all seem pretty uniform (and different from `avsc`), so I wonder if you have an
idea what the integration will look like?
> JavaScript implementation
> -------------------------
>
> Key: AVRO-1747
> URL: https://issues.apache.org/jira/browse/AVRO-1747
> Project: Avro
> Issue Type: Improvement
> Components: javascript
> Reporter: Matthieu Monsch
>
> Hello,
> I'm not sure if there is still interest in a JavaScript implementation of the
> Avro spec, or if this is the right place for this message (apologies if not),
> but in case it's useful here is one: https://github.com/mtth/avsc
> It's pretty fast, fully featured aside from protocols (AFAIK), and runs in
> the browser.
> Disclaimer: I wrote this library. (I initially searched around for existing
> implementations, and even saw a few tickets on this board about JavaScript
> decoders, but couldn't find one to support the schemas I have to process.)
> Best,
> -Matthieu
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
