<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">To understand the "server
infrastructure", you need to read all of the pages at:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><a class="moz-txt-link-freetext" href="https://www.aprs-is.net/">https://www.aprs-is.net/</a></div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">In there you will see:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">
<blockquote type="cite"><span style="color: rgb(0, 0, 0);
font-family: "Times New Roman"; font-size: medium;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: 400; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; white-space: normal;
text-decoration-thickness: initial; text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;">To make this as painless as possible
to APRS software authors at the time, it was decided to use
simple, low-level TCP socket connections and pass CR/LF
delimited lines using the TNC2 monitor format
(SENDER>DEST,PATH:rest of packet).</span></blockquote>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">And because the same format is used for
client connections as for server connections, and the fact that
there are a great many diverse clients and servers out there, some
of which are no longer supported but still in wide-spread use
(read: UI-View), the only thing that is expected and/or propagated
along the APRS-IS connections are actual packets. There is no
room in the existing specification for extension beyond that
because clients are expecting every CR/LF delimited line to be a
packet.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">If you want to start something like
"APRS 2.0", then you'll need to bring your own entire
infrastructure to the table as well. The 100s of existing
APRS-IS servers and clients will likely not appreciate changes in
their underlying packet and connection traffic formats. (Ok,
100s is a slight exaggeration according to
<a class="moz-txt-link-freetext" href="https://status.aprs2.net/">https://status.aprs2.net/</a>)<br>
</div>
<div class="moz-cite-prefix"><br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 8/19/2023 5:48 AM, Borja Marcos
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:28058392-E743-4892-ADCF-E5367E91692C@gmail.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On 18 Aug 2023, at 17:18, Lynn W Deffenbaugh (Mr) <a class="moz-txt-link-rfc2396E" href="mailto:KJ4ERJ@arrl.net"><KJ4ERJ@arrl.net></a> wrote:
Please remember that the "APRS" has NO database! Sites like findu.com and aprs.fi are run by individuals of their own free will on their not-so-free hardware and bandwidth.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
But there is a server infrastructure linking iGates together, or am I wrong?
What I intend is to make all the data more useful.
73,
Borja, EA2EKH
_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>