1. 04 9月, 2013 3 次提交
  2. 03 9月, 2013 2 次提交
  3. 02 9月, 2013 2 次提交
    • R
      Polish WebSocket/STOMP Java config · e21bbdd9
      Rossen Stoyanchev 提交于
      Ensure configuration provided for WebSocketHandler's (eg interceptors,
      or HandshakeHandler) are passed on to the SockJsService if congiured.
      
      Better separate Servlet-specific parts of the configuration to make it
      more obvious where non-Servlet alternatives could fit in.
      
      Add more tests.
      
      Improve WebSocket integration tests.
      e21bbdd9
    • R
      Remove incorrect package import · 5d697005
      Rossen Stoyanchev 提交于
      Issue: SPR-10880
      5d697005
  4. 30 8月, 2013 1 次提交
  5. 29 8月, 2013 5 次提交
  6. 28 8月, 2013 4 次提交
  7. 20 8月, 2013 6 次提交
    • R
      Polish StompBrokerRelayMessageHandler · 68c0df83
      Rossen Stoyanchev 提交于
      68c0df83
    • R
      94fefec0
    • A
      Improve broker availability events · 3fb5ff26
      Andy Wilkinson 提交于
      Use a single class for the broker availability event with a boolean
      that indicates whether or not the broker is available, rather than one
      event for an available broker and one event for an unavailable broker.
      
      Publish broker availability events in SimpleBrokerMessageHandler so that
      it can be used as a drop-in replacement for
      StompBrokerRelayMessageHandler.
      3fb5ff26
    • A
      Add reconnect logic to the relay's system session · 131b5de6
      Andy Wilkinson 提交于
      Upgrade to Reactor snapshot builds to take advantage of TcpClient's
      reconnect support that was added post-M1. Now, the system relay session
      will try every 5 seconds to establish a connection with the broker, both
      when first connecting and in the event of subsequently becoming
      disconnected.
      
      A more sophisticated reconnection policy, including back off and
      failover to different brokers, is possible with the Reactor API. We may
      want to enhance the relay's reconnection policy in the future.
      
      Typically, a broken connection is identified by the failure to forward
      a message to the broker. As things stand, the message id then discarded.
      Any further messages that are forwarded before the connection's been
      re-established are queued for forwarding once the CONNECTED frame's been
      received. We may want to consider also queueing the message that failed
      to send, however we would then need to consider the possibility of the
      message itself being what caused the broker to close the connection
      and resending it would simply cause the connection to be closed again.
      131b5de6
    • A
      Publish events about broker's availability · 8b48d8f4
      Andy Wilkinson 提交于
      Components that are using a StompBrokerRelayMessageHandler may want
      to know whether or not the broker's unavailable. If they're sending
      messages to the relay via an asynchronous channel there's currently
      no way for them to find this out.
      
      This commit enhances StompBrokerRelayMessageHandler to publish
      application events when the broker's availability changes:
      BrokerBecameAvailableEvent and BrokerBecameUnavailableEvent.
      Irrespective of the number of relay sessions only a single event is
      published for each change in the broker's availability.
      8b48d8f4
    • A
      Integration tests for the broker relay · be6dbe54
      Andy Wilkinson 提交于
      be6dbe54
  8. 14 8月, 2013 1 次提交
  9. 02 8月, 2013 1 次提交
    • A
      Introduce SubProtocolHandler abstraction · 9e20a256
      Andy Wilkinson 提交于
      Add SubProtocolHandler to encapsulate the logic for using a
      sub-protocol.
      
      A SubProtocolWebSocketHandler is also provided to
      delegate to the appropriate SubProtocolHandler based on the
      negotiated sub-protocol value at handshake.
      
      StompSubProtocolHandler provides handling for STOMP messages.
      
      Issue: SPR-10786
      9e20a256
  10. 25 7月, 2013 1 次提交
    • A
      Make BeanFactoryMCDR BeanFactoryAware · 4390591b
      Andy Wilkinson 提交于
      SI's BeanFactoryChannelResolver was BeanFactoryAware. This commit
      brings Spring's BeanFactoryMessageChannelDestinationResolver in line
      with the old SI class.
      4390591b
  11. 22 7月, 2013 3 次提交
  12. 20 7月, 2013 1 次提交
    • R
      Revise UserSessionResolver to UserQueueSuffixResolver · 90c4712d
      Rossen Stoyanchev 提交于
      The resolver for /user/{username} prefixed destinations is now
      more explicitly designed to store queue suffixes rather than session
      id's, which is what we happen to use as queue suffixes.
      
      This allows something other than the sessionId to be used without
      having to change many places. It also enables applications to
      construct destinations with user-specific queue suffixes without
      making assumptions about what's used for queue suffixes. For
      example a controller may construct a map with subscription destinations
      and send that down to the client.
      90c4712d
  13. 19 7月, 2013 1 次提交
  14. 18 7月, 2013 5 次提交
  15. 17 7月, 2013 2 次提交
  16. 16 7月, 2013 2 次提交