Giters
swagger-api
/
swagger-socket
Swagger Socket: A REST over WebSocket
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
382
Watchers:
59
Issues:
46
Forks:
59
swagger-api/swagger-socket Issues
swagger-socket still alive?
Updated
6 years ago
Comments count
2
Comments on the API
Closed
7 years ago
Comments count
15
node client doesn't connect
Closed
8 years ago
Comments count
2
Request-Response Only?
Updated
8 years ago
Comments count
1
Wanna use swagger for websocket without REST
Closed
9 years ago
Comments count
1
Do not package a copy of atmosphere.js in swaggersocket.js war
Closed
9 years ago
Make swaggersocket.js more friendly to node.js
Closed
9 years ago
swaggersocket.js inconsistent handling between swagger socket client & protocol
Closed
9 years ago
Comments count
4
The very first response may fail to be processed at the client and a reconnect may require
Closed
9 years ago
Comments count
9
swaggersocket.js fails to send an array of requests
Closed
9 years ago
Can swagger-socket be installed for node via npm?
Closed
9 years ago
Comments count
3
use dataFormat as the content-type
Closed
9 years ago
Comments count
1
[protocol] Add extension support to the protocol
Updated
9 years ago
Setting headers in the request message may result in a corrupted json message
Closed
9 years ago
Comments count
1
Add an osgi wab sample
Closed
9 years ago
Potential issue with concurrent calls
Closed
9 years ago
Make wordnik and twitter nettosphere samples to ask for the API-key from stdin if not supplied
Closed
9 years ago
Create a karaf feature for swaggersocket to simplify its deployment on Karaf
Closed
9 years ago
Make OSGi bundles for swaggersocket-server and swaggersocket-protocol
Closed
9 years ago
Add a node.js sample using swaggersocket.js to talk to samples/swaggersocket-echo
Closed
9 years ago
Comments count
1
Upgrade to jackson2
Closed
9 years ago
nettosphare samples log the wrong port number 8080 even when not running at 8080
Closed
9 years ago
Add an option to specify which headers are transferred to the swaggersocket's response
Closed
9 years ago
Provide a defined behavior in generating a response generated by multiple writes
Closed
9 years ago
Comments count
1
Supporting body-less REST responses in SwaggerSocket
Closed
9 years ago
Comments count
2
Upgrade to atmosphere.js 2.2.8
Closed
9 years ago
update to atmosphere-2.2.6
Closed
9 years ago
The initial heartbeat message may interfere with the subsequent response processing
Closed
9 years ago
Add a plain swaggersocket.js
Closed
9 years ago
Comments count
4
Make jetty version selectable for unit tests and jetty based samples
Closed
9 years ago
The headers building code in Response is inconsistent
Closed
9 years ago
Comments count
1
Allow sample's http server to use a different port than default 8080
Closed
9 years ago
Create additional samples in Java
Closed
9 years ago
Comments count
1
Add a non-jersey based (e.g., cxf) sample
Closed
9 years ago
content-type is to forwarded to the application
Closed
9 years ago
`jetty:run` fails
Closed
10 years ago
Comments count
4
Update Readme with servlet inti param to enable Swaggersockets
Closed
10 years ago
Comments count
1
samples/swaggersocket-twitter needs to be upgraded to use twitter API 1.1
Closed
10 years ago
Comments count
9
Swaggersocket-twitter, onOpen has been invoked first.
Closed
10 years ago
Comments count
1
Add support for Ping/Pong status in the protocol
Closed
12 years ago
Must implement the TrackMessageSizeInterceptor
Closed
12 years ago
Gracefully Support Server Restart
Updated
12 years ago
Allow Client to Define ID
Updated
12 years ago
Add support for remotely closing an active request
Updated
12 years ago
[documentation] Add full site documentation of SwaggerSocket
Updated
12 years ago
Add support for SwaggerSocket on top of the HTTP protocol
Closed
12 years ago