openwire is the de facto standard for ActiveMQ and has been optimised to read/write bytes[] while Stomp (= Streaming Text) should be considered when you do not have any other alternative.
Why would you like to use a JMS C Client and not a Java JMS client ? bcmoney wrote: > > Hi Charles, > > Thanks for the info, yes I did check out the C-integration page it was > where I first started. Do you have any info at all on building on Windows, > or, would I be better off on Linux? > > Mostly I'm in need of some documentation on getting one of them running on > either platform... I think you're right that OpenWire is the most recent > and (possibly?) the most stable. > > Bryan > > > > cmoulliard wrote: >> >> Hi, >> >> Have you checked this web page of ActiveMq wiki site >> >> http://activemq.apache.org/c-integration.html >> >> http://activemq.apache.org/openwire-c-client.html >> >> KR, >> >> Charles >> >> >> bcmoney wrote: >>> >>> Hi, looking in the http://activemq.apache.org/c-integration.html C >>> cross-client implementations >>> http://svn.apache.org/repos/asf/activemq/sandbox/openwire-c/ OpenWire >>> and http://svn.stomp.codehaus.org/browse/stomp/trunk/c/ STOMP C >>> implementations, I see only prototype code, which project would be most >>> easy to get running though? >>> >>> Does anyone have a working example or experience building one of the >>> prototype C implementations (possibly with brief build/run >>> instructions)??? >>> >>> It would be GREATLY appreciated! I need to get a JMS consumer/producer >>> going using C, like yesterday!! >>> >> >> > > ----- Charles Moulliard SOA Architect My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/ -- View this message in context: http://old.nabble.com/Working-C-example--tp28702366p28738450.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
