Important clarification for Smile specification; new patch level (1.0.4)

[Tatu Saloranta]

Quick note: as per this problem report (https://github.com/FasterXML/jackson-dataformat-smile/issues/11), a flaw was found in version 1.0.3 of Smile format specification.

Implementations that I am aware of (Java, C codecs) implement this correctly, so as far as I know this should not create actual data inconsistency. But if you are aware of implementations that used specification as the sole guide, please let me know.

I updated the spec at:

wiki.fasterxml.com/SmileFormatSpec

including patch-level upgrade to 1.0.4.

On better news, it looks like we might be getting another Smile codec implementation, and this for iOS (objective-C). I will share more information if and when codec is publicly released (or perhaps author will share the information first).

-+ Tatu +-

[Sunny Gleason]

Thank you for the heads-up, Tatu! Glad to see the spec is
still active & interesting to so many folks!

I was wondering, what are the most in-demand client libraries?
I'm thinking of possibly pitching in some Smile code this summer.

BTW, I gave Smile a shout out in a presentation on building efficient
key value stores last month. Hopefully I got it right, and more folks
will be getting into Smile! :)

https://speakerdeck.com/sunnygleason/practical-tips-for-using-mysql-as-a-key-value-store

Best regards,

-Sunny

> --
> You received this message because you are subscribed to the Google Groups
> "smile-format-discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to smile-format-disc...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

[Tatu Saloranta]

On Sun, May 12, 2013 at 3:59 PM, Sunny Gleason <sunny....@gmail.com> wrote:

Thank you for the heads-up, Tatu! Glad to see the spec is
still active & interesting to so many folks!

Agreed. And in this case, possible adoption is due to good experience on Android side, with Java codec.
So hopefully success begets success. :)

 

I was wondering, what are the most in-demand client libraries?
I'm thinking of possibly pitching in some Smile code this summer.

I think completing C codec (https://github.com/pierre/libsmile) is at the top of the list, including bindings for other languages. I have gotten requests for Javascript codec as well -- quite a bit more challenging, but apparently browsers nowadays finally have some means to access binary data (plus theres the Node platform, which should have decent binary access anyway).

And C# would make sense.

BTW, I gave Smile a shout out in a presentation on building efficient
key value stores last month. Hopefully I got it right, and more folks
will be getting into Smile!  :)

https://speakerdeck.com/sunnygleason/practical-tips-for-using-mysql-as-a-key-value-store

Great! Thanks for the link, need to read it.

I also presented "Tour de Jackson" (https://docs.google.com/presentation/d/1t4VkFUbQK0JeAZLPCn8ZJ5ij0Q0hIqcgWmRHmjGs5eA/edit?usp=sharing) this week, and included Smile as one of most important lesser-known things Jackson supports.

-+ Tat +-

[Tatu Saloranta]

On Sun, May 12, 2013 at 6:34 PM, Tatu Saloranta <tsalo...@gmail.com> wrote:

On Sun, May 12, 2013 at 3:59 PM, Sunny Gleason <sunny....@gmail.com> wrote:

Thank you for the heads-up, Tatu! Glad to see the spec is
still active & interesting to so many folks!

Agreed. And in this case, possible adoption is due to good experience on Android side, with Java codec.
So hopefully success begets success. :)

 

I was wondering, what are the most in-demand client libraries?
I'm thinking of possibly pitching in some Smile code this summer.

I think completing C codec (https://github.com/pierre/libsmile) is at the top of the list, including bindings for other languages. I have gotten requests for Javascript codec as well -- quite a bit more challenging, but apparently browsers nowadays finally have some means to access binary data (plus theres the Node platform, which should have decent binary access anyway).

And C# would make sense.

BTW, I gave Smile a shout out in a presentation on building efficient
key value stores last month. Hopefully I got it right, and more folks
will be getting into Smile!  :)

https://speakerdeck.com/sunnygleason/practical-tips-for-using-mysql-as-a-key-value-store

Great! Thanks for the link, need to read it.

Forgot one more thing -- would be great to get InnoDB backed single-node store for TransiStore (https://github.com/FasterXML/TransiStore), via StoreMate project.
I have added LevelDB-based along with BDB-JE one; and also playing with LMDB-backed variant. So I would guess that InnoDB-backed variant should be quite easy to do.

-+ Tatu +-

[Rennie Petersen]

> And C# would make sense.

Do you know if anyone is doing anything about this?

Thanks,
Rennie

[Tatu Saloranta]

I am not aware of a project for C# version. Over time, individuals have indicated interest in doing that, but I don't think anything was started based on those discussions.

If anyone else is aware of such codec, please let others know.

-+ Tatu +-