swagger-api/swagger-socket

Issues

• swagger-socket still alive?

  #52 opened 8 years ago by jasonCodesAway
  2

• Comments on the API

  #18 opened 7 years ago by jhthorsen
  15

• node client doesn't connect

  #48 opened 8 years ago by danactive
  2

• Request-Response Only?

  #50 opened 9 years ago by brentarias
  1

• Wanna use swagger for websocket without REST

  #47 opened 9 years ago by artem-korolev
  1

• Do not package a copy of atmosphere.js in swaggersocket.js war

  #46 opened 9 years ago by elakito
  0

• Make swaggersocket.js more friendly to node.js

  #45 opened 9 years ago by elakito
  0

• swaggersocket.js inconsistent handling between swagger socket client & protocol

  #44 opened 9 years ago by johnmerm
  4

• The very first response may fail to be processed at the client and a reconnect may require

  #43 opened 9 years ago by elakito
  9

• swaggersocket.js fails to send an array of requests

  #42 opened 9 years ago by elakito
  0

• Can swagger-socket be installed for node via npm?

  #24 opened 9 years ago by joeyjmorales
  3

• use dataFormat as the content-type

  #41 opened 9 years ago by elakito
  1

• [protocol] Add extension support to the protocol

  #5 opened 12 years ago by jfarcand
  0

• Setting headers in the request message may result in a corrupted json message

  #39 opened 9 years ago by elakito
  1

• Add an osgi wab sample

  #40 opened 9 years ago by elakito
  0

• Potential issue with concurrent calls

  #38 opened 10 years ago by elakito
  0

• Make wordnik and twitter nettosphere samples to ask for the API-key from stdin if not supplied

  #37 opened 10 years ago by elakito
  0

• Create a karaf feature for swaggersocket to simplify its deployment on Karaf

  #36 opened 10 years ago by elakito
  0

• Make OSGi bundles for swaggersocket-server and swaggersocket-protocol

  #35 opened 10 years ago by elakito
  0

• Add a node.js sample using swaggersocket.js to talk to samples/swaggersocket-echo

  #34 opened 10 years ago by elakito
  1

• Upgrade to jackson2

  #33 opened 10 years ago by elakito
  0

• nettosphare samples log the wrong port number 8080 even when not running at 8080

  #32 opened 10 years ago by elakito
  0

• Add an option to specify which headers are transferred to the swaggersocket's response

  #30 opened 10 years ago by elakito
  0

• Provide a defined behavior in generating a response generated by multiple writes

  #28 opened 10 years ago by elakito
  1

• Supporting body-less REST responses in SwaggerSocket

  #27 opened 10 years ago by elakito
  2

• Upgrade to atmosphere.js 2.2.8

  #31 opened 10 years ago by elakito
  0

• update to atmosphere-2.2.6

  #29 opened 10 years ago by elakito
  0

• The initial heartbeat message may interfere with the subsequent response processing

  #26 opened 10 years ago by elakito
  0

• Add a plain swaggersocket.js

  #25 opened 10 years ago by elakito
  4

• Make jetty version selectable for unit tests and jetty based samples

  #23 opened 10 years ago by elakito
  0

• The headers building code in Response is inconsistent

  #22 opened 10 years ago by elakito
  1

• Allow sample's http server to use a different port than default 8080

  #21 opened 10 years ago by elakito
  0

• Create additional samples in Java

  #2 opened 10 years ago by chadlung
  1

• Add a non-jersey based (e.g., cxf) sample

  #20 opened 10 years ago by elakito
  0

• content-type is to forwarded to the application

  #19 opened 10 years ago by elakito
  0

• `jetty:run` fails

  #12 opened 10 years ago by reverofevil
  4

• Update Readme with servlet inti param to enable Swaggersockets

  #4 opened 10 years ago by rpidikiti
  1

• samples/swaggersocket-twitter needs to be upgraded to use twitter API 1.1

  #17 opened 10 years ago by elakito
  9

• Swaggersocket-twitter, onOpen has been invoked first.

  #14 opened 10 years ago by gsuresh92
  1

• Add support for Ping/Pong status in the protocol

  #7 opened 12 years ago by jfarcand
  0

• Must implement the TrackMessageSizeInterceptor

  #11 opened 12 years ago by jfarcand
  0

• Gracefully Support Server Restart

  #10 opened 12 years ago by darkfrog26
  0

• Allow Client to Define ID

  #9 opened 12 years ago by darkfrog26
  0

• Add support for remotely closing an active request

  #8 opened 12 years ago by jfarcand
  0

• [documentation] Add full site documentation of SwaggerSocket

  #6 opened 12 years ago by jfarcand
  0

• Add support for SwaggerSocket on top of the HTTP protocol

  #3 opened 12 years ago by jfarcand
  0