Hi, yeah it seems that HttpTransport and HttpsTransport classes has been obsolete. Do you need them for some reason? We should probably mark them as obsolete.
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Oct 19, 2010 at 10:22 PM, schow <[email protected]> wrote: > > Hi, > > We're working through some issues with the HTTP transport when connecting a > network of brokers over a periodically failing network. In the process, > I've noticed that there are two implementations of the HTTP transport: > HttpTransport and HttpClientTransport. > > HttpClientTransport was made the default implementation of HTTP by this > checkin: > > Revision: 359551 > Author: jstrachan > Date: 7:38:10 AM, December 28, 2005 > Message: > use commons-httpclient by default > ---- > Modified : > /incubator/activemq/trunk/activemq-optional/src/main/java/org/activemq/transport/http/HttpClientTransport.java > Modified : > /incubator/activemq/trunk/activemq-optional/src/main/java/org/activemq/transport/http/HttpTransportFactory.java > Modified : > /incubator/activemq/trunk/activemq-optional/src/main/java/org/activemq/transport/http/HttpTunnelServlet.java > > While looking through the implementation of HttpTransport, I noticed that it > does not issue the HEAD command at startup, which is done by > HttpClientTransport. > > This makes me wonder whether HttpTransport has been kept up-to-date with > changes or is HttpClientTransport not only the default, but also only, > current implementation of the HTTP Transport? > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Is-HttpTransport-up-to-date-tp3002747p3002747.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
