Hi Nelson
-protocol SOCKET
switches both the connection and the callback to SOCKET.
Cheers
Michele
inEvo wrote:
inEvo wrote:
Is there any way to use the client's IP as the Callback address
without having to supply it ?
Ok .. got it working using SOCKETs but the default protocol is CORBA and
i do
Am I understanding you right ? Would you write a WebServices client to
make xmlBlaster act as a webservices provider ?
Michele
inEvo wrote:
Hi,
Can i provide a WebServices frontent to subscribe user to a given topic?
Users would invoke a WebService stating their address, protocol to be
used, cal
inEvo wrote:
Is there any way to use the client's IP as the Callback address
without having to supply it ?
Ok .. got it working using SOCKETs but the default protocol is CORBA and
i don't get any callbacks ...
Is there any way to use the client's IP as the Callback address without
having to supply it ?
Hi,
Can i provide a WebServices frontent to subscribe user to a given topic?
Users would invoke a WebService stating their address, protocol to be
used, callback funtion and corresponding topic and the servr would then
perform their login and start sending them the messages they subscribed
using
Thanks.
Yesterday I had a lot of fun learning all about docbook... It looks like a fine
specification.
Now, onto the nitty gritty of trying to define exactly what information someone
would need from a tutorial book... Some of this I can rely on intuition, as
Michele said, as a newbie to the
Hi,
What would be the best place to send textual info ? Having the messgae
split in 3 parts should "enforce" some best practices... In the demos
i've seen you seend strings in the content using getBytes()... but this
could have gone in the topic as well as in the QoS.. are there any
guidelines
Hi,
it looks like there are some pretty fine thoughts and ideas comming up.
I love reading this thread.
If you need some aid on the server side, let me know.
Heinrich
On Tue, 25 Jan 2005, Dupuy, Robert wrote:
>
> >>So if I understood you correctly now you identified two different
> tasks:
> >>-