Hi,
Say we have a machine with several network interfaces and Synapse is running
on it. Is it possible to bind some of these interfaces to Synapse nhttp
transport server side and some of them to nhttp transport client side. For
example is it possible to bind to 2 network interfaces from the server
Hi Ruwan,
thanks for your response. As described earlier it is perfectly clear to me that
the usage of LinkedHashMaps would not solve the „problem“ entirely as the order
of top level elements might still change. On the other hand the more annoying
problem is the order of the elements below the
Hi Supun
> Say we have a machine with several network interfaces and Synapse is
> running on it. Is it possible to bind some of these interfaces to
> Synapse nhttp transport server side and some of them to nhttp
> transport client side. For example is it possible to bind to 2 network
> interfaces f
[
https://issues.apache.org/jira/browse/SYNAPSE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775410#action_12775410
]
Hiranya Jayathilaka commented on SYNAPSE-596:
-
I have checked in the changes a
[
https://issues.apache.org/jira/browse/SYNAPSE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiranya Jayathilaka reassigned SYNAPSE-458:
---
Assignee: Hiranya Jayathilaka
> Allow the property mediator to set Boolean p
On Tue, Nov 10, 2009 at 2:56 PM, Hubert, Eric wrote:
> Hi Ruwan,
>
>
>
> thanks for your response. As described earlier it is perfectly clear to me
> that the usage of LinkedHashMaps would not solve the „problem“ entirely as
> the order of top level elements might still change. On the other hand
Hi Ansnka,
Can you please point me to the configuration for server side? Is it in the
nhttp.properties file or axis2.xml?
Thanks,
Supun..
On Tue, Nov 10, 2009 at 6:26 PM, Asankha C. Perera wrote:
> Hi Supun
> > Say we have a machine with several network interfaces and Synapse is
> > running on
Rethinking about the serialization process and the object store structure might
also be a good thought.
Yeah, I will investigate into this and propose a solution to fix the entire
problem.
Great!
Enhancing on this part could also ease the process of writing custom mediators.
Writing factories/s
Hi Supun,
Asankha is referring to the parameter “bind-address" of transportReceiver in
axis2.xml.
Please refer to
http://people.apache.org/~veithen/synapse/transports.html#Transport_listener_parameters
for more detail!
Regards,
Eric
PS: Once again many thanks to Andreas for improving the
Hi,
If I understood the configuration correctly it can bind to one
interface/network address or all of them. Is there a way to bind to
something like to 2 out of 4 interfaces?
Thanks,
Supun..
On Tue, Nov 10, 2009 at 11:02 PM, Hubert, Eric wrote:
> Hi Supun,
>
>
>
> Asankha is referring to the
Hi Supun,
I think your understanding is correct and there is currently no way to address
this requirement (if it is one).
The ListeningIORector of HTTP Core NIO is used with one ListenerEndpoint. I
guess one would need to extend HttpCoreNIOListener to support multiple
ListenerEndpoints. Actua
Hubert, Eric wrote:
Hi Supun,
I think your understanding is correct and there is currently no way to
address this requirement (if it is one).
The ListeningIORector of HTTP Core NIO is used with one
ListenerEndpoint. I guess one would need to extend HttpCoreNIOListener
to support multi
Hi Oleg,
Thanks for the tip. I'll add several endpoints to IOReactor to listen and
try to see weather it is working.
Thanks,
Supun..
On Wed, Nov 11, 2009 at 2:56 AM, Oleg Kalnichevski wrote:
> Hubert, Eric wrote:
>
>> Hi Supun,
>>
>>
>> I think your understanding is correct and there is curren
13 matches
Mail list logo
