okk actually the scene is that we r not sure what protocol we might encounter at client site so we have to be prepared for as much support as we can give.
Thats the probs as i don't know how to go about it . Even google didn't gave any good result cause i need to give the authentication on the client site and not on the server site as we are making it as mesage-broker vendor neutral.. so can't depend on server to provide the authentication part :D James.Strachan wrote: > > On 4/12/07, rachit goel <[EMAIL PROTECTED]> wrote: >> >> To be very frank it could be any . > > What do you mean 'any protocol'? Its pretty hard to write an 'any > protocol' transport implementation :) So you need to pick some > protocol first and try it out. > > AFAIK SSL should do the trick > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Help-with-JMS-client-app-authenticating-to-a-firewall-or-proxy-tf3552547s2354.html#a9961266 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
