synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hubert, Eric" <eric.hub...@jamba.net>
Subject RE: Making force HTTP 1.0 a part of the endpoint definition?
Date Thu, 17 Jul 2008 11:50:03 GMT
Hi all,

 

sounds like an interersting idea. We actually define it in exactly that
way on an endpoint level in our custom "repository" and generate a
synapse.xml containing the property mediator to set this property. It
would be more straightforward to be able to set this at the endpoint
level. There one should consider LoadbalanceEndpoints as a kind of
container from which "child endpoints" should inherit the defaults.
Right now some properties need to be specified at the individual
endpoint level like suspend duration and timeout. Most of the time all
endpoints of a loadbalancing group should be handled in the same way
(either all http 1.0 or all http 1.1 etc.) Just a thought...

 

Regards,

   Eric

 

________________________________

From: Asankha C. Perera [mailto:asankha@wso2.com] 
Sent: Thursday, July 17, 2008 1:08 PM
To: dev@synapse.apache.org
Subject: Re: Making force HTTP 1.0 a part of the endpoint definition?

 

Paul

Infact I was thinking of the same thing.. and was suggesting to Ruwan
about allowing properties to be set at an Endpoint level.. and the most
useful properties could be for HTTP 1.0. use of just the PATH instead of
full URL, setting JMS reply destinations etc..

asankha

Paul Fremantle wrote: 

I'm generally against hard-coding transport specifics, but the high
number of people running into trouble with HTTP1.0-only servers makes
me wonder if its worth us adding a flag to the endpoint definition to
force HTTP 1.0?
 
Thoughts?
 
Paul
 
  

 

-- 
Asankha C. Perera 

WSO2 - http://wso2.org
http://esbmagic.blogspot.com


Mime
View raw message