On 04/13/2010 08:19 AM, Gordon Sim wrote:
On 04/12/2010 10:30 PM, Rajith Attapattu wrote:
Hi All,
Judging by some of the questions on the user list, I feel we could do
a much better with our examples.
(Also our examples should be more visible in the source tree and
easily accessible from our release artefacts.
However I believe that is a different discussion for another day.)
I am envisioning the following structure for the examples, and most of
the old examples can be easily adapted to the new format.
1. store-and-forward.
2. pub/sub with topics
3. request-reply
4. map messages
5. using flow control
6. * using addressing options (multiple examples showing binding to
multiple exchanges, create/delete/assert options ..etc)
7. using SSL/Kerb encryption
8. Authentication (ex. Kerberos, external)
9. using failover
10. transactions
* Maybe drain and spout could be used for this (as is or with some
modifications) ?
I think drain and spout should be used for 1. and 2. as well, also for
9. and even to a lesser extent for 4.
I agree for 1, 2, and 9.
To me, map messages are distinct, the code will look different enough to
be worth a separate example.
I don't think 7. and 8. require a separate example. It is just a
configuration issue. Ideally all the examples should work using
different authentication configuration and we need some clear and
accessible documentation on how to do that rather than new examples.
The same is probably true for SSL.
Agreed - though I wonder if example shell scripts and batch files could
be helpful for some of this.
The examples should be simple.
I think one of the problems is that all the examples are very simple.
Having simple examples is certainly important. However to my mind some
of the questions raised might be better answered by a slightly more
involved example, e.g. the reservations example in python.
My suggestion is:
(a) we get rid of the old amqp 0-10 specific examples
(b) we have a simple helloworld example in each language
(c) we have spout and drain to show different messaging patterns
(d) we have a client-server example (to show use of reply-to and
creation or temp reply queues)
(e) maybe have a dedicated map message example (not totally sure this
is needed)
(f) we start trying to build out the reservations example as a more
complete program
(g) we describe how to run at least spout and drain using
authentication, SSL etc
This makes sense to me.
Perhaps sample shell scripts and batch files in the drain/spout
directories would be helpful for (g).
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
