Issue 10 in sipana: Replace agent sender from JMS to HTTP

0 views
Skip to first unread message

codesite...@google.com

unread,
Feb 17, 2009, 10:55:32 PM2/17/09
to sipan...@googlegroups.com
Status: Accepted
Owner: marcoshack
Labels: Type-Enhancement Priority-High Milestone-v0.4 Component-Agent

New issue 10 by marcoshack: Replace agent sender from JMS to HTTP
http://code.google.com/p/sipana/issues/detail?id=10

Use RESTEasy client API to send messages from the agents to the server
using REST webservices, replacing the current JMS sender implementation.


--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

codesite...@google.com

unread,
Feb 17, 2009, 11:15:36 PM2/17/09
to sipan...@googlegroups.com

Comment #1 on issue 10 by marcoshack: Replace agent sender from JMS to HTTP
http://code.google.com/p/sipana/issues/detail?id=10

GZIP encoding/decoding support was added to RESTEasy client API. It would be
interesting to use it on agent message sending to decrease the data
transfered over
the network, but it's necessary to evaluate the CPU usage.

http://sourceforge.net/mailarchive/forum.php?thread_name=49938184.9090502%40redhat.com&forum_name=resteasy-developers

Reply all
Reply to author
Forward
0 new messages