On 04/13/2010 12:02 PM, Gordon Sim wrote:
On 04/13/2010 04:36 PM, Rajith Attapattu wrote: While drain and spout
are excellent for demonstrating these aspects
they are not necessarily good code examples.
While the python is nice and compact the c++ and and the JMS based
versions are not !
I would argue that the issue to be dealt with there is some
restructuring of the example code (e.g. moving the options handling
code) to make it more readable.
I agree.
The ability to provide an address on the command line is really nice for
writing tutorials, as long as the code is simple.>
How many times have seen people asking about how to do flow control
and acking etc.. ?
People are looking for specific code segments that are easily
identified in the example.
I think better reference documents are the real solution here.
I do think an example would be helpful here.
While the latter is difficult, at least the SSL one could be easily
done.
The configuration matters and can be easily shown in the shell script
etc..
The script can use code from another example.
If - in addition to clear documentation on the approach - you provide
a script for creating test certs and setting up env vars accordingly,
fair enough. I don't see any need to tie that to a specific example
though.
+1
drain / spout (sender/receiver?) are good for this.
I see this as a merging of a simple sender and a simple receiver
program into a single program that sends itself a message. I don't
think any information is lost, and the resulting example is smaller
and easier to take in through a single glance.
I think the tutorial needs this. And if it's in the tutorial, I want it
tested along with the other examples.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
