Le 10/11/2014 20:52, Sven Van Caekenberghe a écrit :
Just for the record (I am being pedantic here, sorry): STAMP is a STOMP client, a way to connect to a message queue; but in messaging speak the parties are called producers and consumers, not client and servers (although this qualification can be useful architecturally); to run any code you always need both or not much will happen.
Sven
okok, didn't you forgot brokers ? I know but thank you anyway I should have untitled it 'Stamp, RabbitMQ and other MQ systems' not 'Stamp and other MQ systems', but the Rabbit went away, sorry :) just that I'm thinking of writing a small STOMP server may be within the Stamp package. Because to me stamp was a package name not a stomp client, if your feeling is that it is a client may be this package should not have a server or server benchs in it? I can put it outside, I don't mind, and the benchs too with the server (also that I do not want to break or dirty your work Sven) as I previously said, it has no sense from a client perspective. the benchs are done in that perspective : a way to compare performance of different servers, not to bench the stamp client performance (which is important too , but to do that I would have written the bench in java and C too, to bench Stamp client against java and C client. what I don't think I will). mmm... I did well to ask Alain