Hi Gordon,
< wrote:
> On 05/27/2014 03:56 PM, Alexander Yakovets wrote:
>
>> I agree it looks like qpidmessaging.dll from qpid 0.26 with proton 0.6 do
>> not support listening for incoming connection client but maybe future
>> versions will be capable for this? Does qpid architecture suppose this
Hey Gordon,
Kind of related to this thread really, but one thing I mentioned a
little while back was whether it'd be possible to "modularise" qpidd.
What I mean is that although clearly qpidd has been around for a while
and is clearly a broker :-) it also contains a whole bunch of features
th
On 05/27/2014 03:56 PM, Alexander Yakovets wrote:
I agree it looks like qpidmessaging.dll from qpid 0.26 with proton 0.6 do
not support listening for incoming connection client but maybe future
versions will be capable for this? Does qpid architecture suppose this
functionality? Or any communicat
Thanks Gordon,
I agree it looks like qpidmessaging.dll from qpid 0.26 with proton 0.6 do
not support listening for incoming connection client but maybe future
versions will be capable for this? Does qpid architecture suppose this
functionality? Or any communication via qpid::messaging API must inc
On 05/26/2014 09:44 PM, Alexander Yakovets wrote:
I can see qpid-proton.dll is included in
qpid-messaging.dll and I think it should be possible to get connected 2
peers with qpidmessaging.dll without any broker running. But I failed to
get this connectivity, looks like every time I need broker ru
Hello,
Trying to get brokerless connection between 2 peers using qpid 0.26 which
include proton 0.6. Before compiled Proton 0.6 (qpid-proton.dll), all
examples P2P connectivity run well. Then compiled qupidtypes.dll,
qpidcommon.dll, qpidclient.dll, qpid-messaging.dll and qpidd.exe (broker)
and all
