>
> There's always a better way and always a simpler way to do anything but
> not always both at the same time :-)
>
I find everything's getting more inferior and harder at the same time.
But the good news is that a sanity check using a TcpListener and TcpClient
pair works the way I want between
There's always a better way and always a simpler way to do anything but not
always both at the same time :-)
--
noonie
On 11 October 2017 at 15:49, Greg Keogh wrote:
> What logging information are you sending? There is a shit ton of services
>> in Azure for logging out of
>
> What logging information are you sending? There is a shit ton of services
> in Azure for logging out of the box.
>
It's blobs of XML from various programs. Good point about Azure logging,
which I haven't investigated. In my case the logging output doesn't need to
be persisted, clients can
Greg,
UDP isn't inherently unsuitable but you have to do a lot of extra work to
get it going. Especially if you need to guarantee delivery. We use it for
comms in our mobile apps and it meets our needs better than tcp.
David
"If we can hit that bullseye, the rest of the dominoes
will fall
What logging information are you sending? There is a shit ton of services
in Azure for logging out of the box.
On Wed, 11 Oct 2017 at 14:32 Greg Keogh wrote:
> Thanks, chaps you've confirmed that UDP is not suitable, and my further
> reading supports that. I'm running some
Thanks, chaps you've confirmed that UDP is not suitable, and my further
reading supports that. I'm running some experiments with the TcpClient and
TcpListener classes and they are working now on the same machine. The next
test is to put them on different machines on the LAN, then put the server
on
Greg,
If i understand your intention correctly, I can't imagine that working.
Even if it did, it wouldn't be a good idea. The UDP packets would be
blocked at any number of points along the way and probably wouldn't get
far. Maybe even get black listed?
I would suggest clients need to register
UDP is not a connection oriented protocol. The client just sends to the
server on a desired port. That's it.
When you say "broadcast logging information" do you mean you are sending a
datagram to the broadcast address? If so, broadcasts stop at the IP subnet
boundary.
On Wed, 11 Oct 2017 at
I just want to check this is possible...
A server program running in my Azure VM will use the UdpClient class to
broadcast logging information using a chosen port. It doesn't know anything
about who might want to listen.
Client programs anywhere in the world know the IP address and port, and