🚀 go-pugleaf

If you can make a COM server broadcast without needing a request from a
client
can you tell me how you did it? Borland support says it can't be done.
( Remember it's an UNSOLICITED broadcast I'm after, no client involvment
other than receiving )

I have multi-threads running already so that part you could skip.
I have a server client demo running also, so the only thing I need to see is
how you get
around the server's need for the request from the client.

BTW, I don't even need to send any "data" I just need the server to fire an
event in the client.
That event will already contain everything the client needs.

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:43599f5f$1@newsgroups.borland.com...
>
> "Gary D" <gcdesroches@nctc.com> wrote in message
> news:43599303@newsgroups.borland.com...
>
>> Is a socket the best way to do this?
>
> A socket is one way to do it.
>
>> I have looked into COM and found that COM servers
>> will not broadcast an unsolicited message.
>
> Yes, they will.  I have COM servers that broadcast events just fine.
>
>> the server will have to do extra work holding open a triggered
>> event until something happens to complete the sequence.
>
> Use multiple threads.  Have one thread monitoring the events, then have
> another thread that broadcasts events to clients.  When a monitored event
> occurs, copy the relative information to a queue in the broadcast thread 
> and
> then go back to monitoring for new events.  This way, the broadast thread 
> is
> run in parallel to the monitoring thread and the monitoring is not waiting
> for the broadcast to finish, and vice versa.
>
>
> Gambit
>
>