Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: STOMP-3
Type: Sub-task Sub-task
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Hiram Chirino
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Forge: Stomp
STOMP-1

Stomp connection should be easy to discriminate

Created: 15/Jul/09 01:18 PM   Updated: 15/Jul/09 01:18 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None


 Description  « Hide
In STOMP 1.0, all client connections start with:
CONNECT

That makes it very hard to discriminate a STOMP connection from an HTTP connection since CONNECT is valid HTTP verb too. This makes it hard to build a sever that can accept different types of protocols on one port.

Perhaps it would be better if STOMP 1.1 starts with an Protocol info frame before the CONNECT frame. For example:

STOMP
version=1.1

^@
CONNECT

^@


 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.