You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@synapse.apache.org by ve...@apache.org on 2008/05/21 12:33:20 UTC

svn commit: r658620 - /synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/udp/package-info.java

Author: veithen
Date: Wed May 21 03:33:20 2008
New Revision: 658620

URL: http://svn.apache.org/viewvc?rev=658620&view=rev
Log:
Added two items to the known issues and limitations of the UDP transport.

Modified:
    synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/udp/package-info.java

Modified: synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/udp/package-info.java
URL: http://svn.apache.org/viewvc/synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/udp/package-info.java?rev=658620&r1=658619&r2=658620&view=diff
==============================================================================
--- synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/udp/package-info.java (original)
+++ synapse/trunk/java/modules/transports/src/main/java/org/apache/synapse/transport/udp/package-info.java Wed May 21 03:33:20 2008
@@ -81,6 +81,16 @@
  *       When SOAP with WS-Addressing is used, the packets could be
  *       received on a single port and dispatched based on the <tt>To</tt>
  *       header. This is not supported.</li>
+ *   <li>It might be useful to allow configuration of the content type at the
+ *       transport level rather than the service level. In this case, the
+ *       <tt>contentType</tt> parameter would not be included in the endpoint
+ *       reference. This is necessary for interoperability with the SOAP over UDP
+ *       standard.</li>
+ *   <li>Technically, it would be quite easy to support binding several UDP ports
+ *       to the same service. However, the way endpoints are configured
+ *       at the service level doesn't allow this for the moment. Indeed,
+ *       using simple text properties only allows to specify the configuration
+ *       of a single endpoint.</li>
  *   <li>The transport sender uses a randomly chosen UDP source port. Some
  *       UDP based services may check the source port and discard the packet.
  *       Also, in two-way communication scenarios, stateful firewalls will