activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mittler, Nathan" <nathan.mitt...@sensis.com>
Subject RE: JMS C/C++ client without a java proxy
Date Wed, 30 May 2007 13:10:02 GMT
 
> 
> 1. Regarding the links for activemq-cpp on your website, URL:
> http://activemq.apache.org/cms.html:
> 
> 
> Overview
> 
>     * Index
>     * News
>     * Getting Started -> refers to the same website
> (i.e.http://activemq.apache.org/cms.html)
>     * API -> refers to the same website
> (i.e.http://activemq.apache.org/cms.html)
>     * FAQ -> refers to the same website
> (i.e.http://activemq.apache.org/cms.html)
>     * Download -> refers to the same website
> (i.e.http://activemq.apache.org/cms.html)
> 
> 

These links work fine for me.  I think what might be happening is that
you clicked on the API link which takes you to
http://activemq.apache.org/cms/html/ ... Once you're here, the site gets
in a funky state where none of the links work.  I've updated the site to
fix this link, it should be fixed in an hour or so.  For now, if you
avoid the API link, you should be fine.

> 
> Using ActiveMQ-CPP
> 
>     * Getting Started -> leads directly to the activemq 
> getting started document 
>     * Example -> The requested URL /example.html was not 
> found on this server.
>     * Configuring -> The requested URL /configuring.html was 
> not found on this server.
> 
> 
> The links you posted:
> 
> http://activemq.apache.org/cms/configuring.html
> http://activemq.apache.org/cms/example.html
> 
> do work....
> 
> 2. I looked at the example ( my C experiences is really a 
> __long__ time ago), but to me it seems that activemq-cpp is 
> more of an API - which itself is based on CMS -  than of a client?
> 
> So, writing an appropriate Client which uses activemq-cpp is 
> up to the user, right?
> 

Actually, CMS is the API.  CMS is a set of interfaces (pure-virtual
classes) that are implemented by ActiveMQ-CPP.  CMS is the "face" of
ActiveMQ-CPP to the user.  Behind the scenes, ActiveMQ-CPP supports a
pluggable architecture (another set of internal APIs) that allows it to
support multiple transports and protocols, but all of that is abstracted
from the user by the CMS API.  The user does not need to write a client,
activemq-cpp is the client.  Out of the box, it will allow them to talk
to a stomp or openwire broker (e.g. ActiveMQ).  It may be extended to do
more, but only if the user REALLY needs/wants to.

Nate



Mime
View raw message