Order Tray | Contact Us | Home | SIG Lists

[aprssig] APRS Message Idea

A.J. Farmer (AJ3U) ajfarmer at spenet.com
Thu Mar 3 15:09:17 UTC 2005

That's what I proposed.  A separate messaging system - not a change in the
current APRS messaging system.  Please read my *entire* original post.

-----Original Message-----
From: aprssig-bounces at lists.tapr.org [mailto:aprssig-bounces at lists.tapr.org]
On Behalf Of AE5PL Lists
Sent: Thursday, March 03, 2005 6:47 AM
To: TAPR APRS Mailing List
Subject: RE: [aprssig] APRS Message Idea

This should not be done for all messaging.  Quite simply, APRS is a
real-time protocol and APRS messaging is also real-time.  When I send a
message, I need to know that it was delivered for a fact, not that it
was attempted and may be attempted later.

Now, that said, setting up a store-and-forward system which can be
specifically requested (like EMAIL) is a workable idea.  This would not
affect standard messaging (not a good idea to modify the messaging
protocol without the user's knowledge).  Something like a server
responding to SANDF or something similar with the requested receiving
station's call as the first thing in the text (like how EMAIL works).
Commands such as "kill" messages might be worthwhile, as well.

Please don't try to modify the APRS messaging protocol for those who do
not request it.  This would be disastrous for the reliability and
usability of APRS-IS.


Pete Loveall AE5PL
mailto:pete at ae5pl.net 
> -----Original Message-----
> From: Andrew Rich (VK4TEC)
> Posted At: Thursday, March 03, 2005 3:27 AM
> Subject: RE: [aprssig] APRS Message Idea
> Like a SMSC Short Message Service Center
> 1) Takes messages in globaly and attempts to deliver on 
> hearing a station
> 2) or Takes messages in globbaly and attempt to deliver on a 
> retry basis
> or both 

aprssig mailing list
aprssig at lists.tapr.org

More information about the aprssig mailing list