<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 10/2/2011 1:40 PM, Stephen H. Smith wrote:
<blockquote cite="mid:4E88A226.2060905@aol.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
One of the features that is unique (as far as I know) to UIview is
it's TCP/IP "local server". Everything UIview hears from the
attached radio/TNC --and/or-- it's Internet APRS-IS login is
replicated at a local TCP/IP server port. In turn, other APRS
clients and applications on the same LAN can connect to to the
local server in exactly the same way they would to the Internet
APRS-IS. This local server port is fully bi-directional.
Other users on the LAN can send messages either to RF (via the
UIivew host's radio/TNC), --or-- to stations on the APRS-IS --or--
to other stations on the LAN. <br>
</blockquote>
<br>
UI-View is not unique in this area. According to the eyechart at
<a class="moz-txt-link-freetext" href="http://www.eskimo.com/~archer/aprs_capabilities.html">http://www.eskimo.com/~archer/aprs_capabilities.html</a>, in the
category "Provides local APRS server socket", APRS+SA, OziAPRS,
UI-View, USA PhotoMaps, and xastir provide this capability.<br>
<br>
APRSISCE/32 in development mode now also supports a downstream
IS-Server port. This port supports full APRS-IS filters and also
forwards packets upstream provided that the downstream client
supplies a valid APRS-IS password. I need to get the current
capabilities sent out to Curt for an update.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32<br>
<br>
</body>
</html>