is sockjs-go worked on?

[notedit]

i see there are two month after last commit. and there are sitll some error on tests.

[igm]

yes, I'm working on this sporadically. I need to introduce some API breaking changes and that's why the project was stalled for some time. However I've adopted http://gopkg.in approach and from now on current implementation is accessible via "gopkg.in/igm/sockjs-go.v1/sockjs" import path which takes code from branch "v1". Please note that not much further development will happen here in v1.

Further development will continue in "master" branch and can be imported as "gopkg.in/igm/sockjs-go.v0/sockjs". Version 0 will introduce API changes and will break current builds eventually. Later the plan is to introduce branch "v2" as soon as the new API stabilises.

[notedit]

thanks. i am working on a realtime app. the sockjs nodejs and python server works well, but i really hate the callbacks.

i want to knew whether you are using sockjs-go in product.

[igm]

I'm not using it in production and using it in production is discouraged (as stated here: https://github.com/igm/sockjs-go#important)
Version 2 will be a complete reimplementation of the library with slightly different API and hopefully production ready, but without any ETA at this moment.

[notedit]

any details on the new version? maybe i can do some help

[igm]

I've branched out previous version into "v1" branch and put new version into master. As I wrote before it is a complete rewrite of library, with less code (with tests) and with proper CI setup. The API is different, but IMO more logical and fits better the sockjs string frame-ing. Any help is more than welcome, I hope (and plan) to release it as a stable and production ready "v2" soon.

[druska]

Great news, @igm. I look forward to v1.

[igm]

thanks @druska , actually it's a version "v2" to look forward ;) I don't expect much activity in "v1"

[iwanbk]

@igm

I'm not using it in production and using it in production is discouraged (as stated here: https://github.com/igm/sockjs-go#important) 
Version 2 will be a complete reimplementation of the library with slightly different API and hopefully production ready, but without any ETA at this moment.

It is production ready now?

[igm]

@iwanbk
Current version 2 is the latest stable with better quality than v1. As with any (not only) open source project, you might encounter problems in the library, if you find any issues, please open a github issue here and we'll work on it, or feel free to submit a PR.