So what happens if the connection between D-PRS Interface and the APRS-IS server goes away? Lets say my Internet service provider drops my connection temporally and then it comes back a few minutes later? (This happens to me all the time on my fixed point wireless Internet service out here in very rural America.) Does D-PRS Interface have the capability to re-establish the connection to the APRS-IS server if the connection is lost?
Mark (KB9KHM) --- In [email protected], "Peter Loveall" <p...@...> wrote: > > --- In [email protected], "kb9khm" <kb9khm@> wrote: > > > > It seems like if I specify a TCP Port for D-PRS Interface to connect > > to (I'm talking TCP "serial port" here - as in connecting to > DVTool), > > that D-PRS Interface will only try once to connect to the TCP port > > when the application is first launched. > > D-PRS Interface is a Windows GUI encapsolated javAPRSSrvr (APRS > server software). The TCP port interface in javAPRSSrvr is > specifically designed to connect to a reliable (always there) TCP > port that presents pure "serial" data. Because this software is > written in Java, there is no ability to know why a connection goes > away other than it was terminated (what we give up to be able to be > platform independent). > > I believe the assumption that a Windows GUI progrm can be started > after the TCP port becomes available is a valid one. The software > that uses the TCP port code relies on the the interface to either be > there or not at startup and would require a major rewrite of more > code than the TCP port code. > > 73, > > Pete Loveall AE5PL >
