Swagger socket for node.js

[nodejs]

Hi!

Is there an implementation of SwaggerSocket for Node.js in the works.

Thanks

[tony tam]

I'd love that :)  It shouldn't be too difficult to do but it's not in our immediate plans.  There are some folks in the community who might help us accelerate that process--as you see in the protocol spec, it's quite simple.

Tony

[Paul Hill]

Do you know of any Node.js implementations in the wild?

I'm likely heading down this path shortly.

[tony tam]

Hi Paul, none that I know of, but it should be easy to implement the subprotocol with socket.io:

https://github.com/wordnik/swaggersocket/wiki/SwaggerSocket-Protocol

[Brian Tan]

Hi all,

I am looking forward to this too but so far, I am quite baffled and confused by the entire swagger-socket approach.

How are we expected to use this especially in a top-down approach where we write the swagger specs using swagger editor and then hook it up with the controllers etc.

Correct me if I am wrong but the current Swagger 2.0 specs do not include support for socket right ?

If yes, then are there plans to include this ?

If no, then can point me to the right resource ?

Currently, I have a NodeJS API designed using Swagger and hooked up to MongoDB using Mongoose which is a pleasant experience for me personally. I love what Swagger did for me (i.e. the auto-documentation, basic validation etc.)

However, I have a new requirement to include support for socket.io  (to provide a simple chat service) and I am kind of lost on how to include this as part of the current Swagger design.

Thanks in advance.

Best Regards,

Brian 

[tony tam]

Hi Brian,

Thanks for resurrecting this post :)  As much as I'd like to get swagger sockets implemented on other platforms, I'm afraid the swagger-api team doesn't have the bandwidth to do so.  I think the idea is solid and someone will make it work but it's going to take a community contribution to do so.

[Brian Tan]

Hi Tony,

Thanks for the prompt reply. I will talk to my manager to see whether the company is willing to contribute back on this.

Best Regards,

Brian Tan

--
You received this message because you are subscribed to a topic in the Google Groups "Swagger" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/swagger-swaggersocket/hZ3Tk7IhQXs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to swagger-swaggers...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aki Yoshida]

Regarding swaggersocket for node.js, the current swaggersocket.js uses
atmosphere.js 2.2.12 and this works for the older node.js but not for
the current v4.

A sample code for using swaggersocket.js on node.js is available here.
https://github.com/swagger-api/swagger-socket/tree/master/samples/swaggersocket-echo-node-client

We have recently updated atmosphere.js and its current 2.2.13-SNAPSHOT
works with v4 and we are planning for a release this week.
Once this new version of atmosphere.js is uploaded to the npm repo,
the above swaggersocket.js node sample should work with node v4.

> You received this message because you are subscribed to the Google Groups
> "Swagger" group.
> To unsubscribe from this group and stop receiving emails from it, send an