Just use HTTP and REST. It works in all languages. You can define
commands as URLs. You can post your log entries as ADIF file snippets.
Use a port other than port 80 for obvious reasons. Most modern
languages have a great HTP client library so you don't have to roll your
own client for yo
Simon,
The gospel according to Microsoft:
[Network DDE is no longer supported. Nddeapi.dll is present on
Windows Vista, but all function calls return NDDE_NOT_IMPLEMENTED.]
Jim VA3HJ
Simon Brown wrote:
>
> An advantage of UDP is that the logger could be on another platform /
> computer. Althou
TCP is reliable. UDP is unreliable.
Aside from sending data that can be safely dropped, such as sound
packets, there is no reason for aplication programs to use UDP.
Leigh/WA5ZNU
On Fri, 1 Feb 2008 5:07 am, Simon Brown wrote:
> An advantage of UDP is that the logger could be on another platform /
BTW - I have a fine NTPClient class in C++ in case anyone is interested, I
use this when calibrating soundcards and also to keep my computer clock
updated every 15 minutes.
You would have to modify it yourself as it uses a few DM780 calls but the
intelligence you need is in place.
Simon Brown,
An advantage of UDP is that the logger could be on another platform /
computer. Although there's network DDE I have never tried it and don't want
to try it to be honest.
Also I would say that UDP is easy in all languages, DDE is a tad complex in
C++.
Simon Brown, HB9DRV
- Original Message
Dave, over five years ago now, I pushed for using a standard DDE interface
for all PSK31 programs so anybody could use his favorite logging probgram
with his favorite PSK31 program, and developers did not have to keep
reinventing the wheel. It also found little interest. :-(
I'd still like to s
