[htaprs] VC-H1 APRN network
Robert Bruninga bruninga at usna.eduWed Feb 27 17:14:07 UTC 2008
- Previous message: [htaprs] VC-H1
- Next message: [htaprs] VC-H1 APRN network
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> I didn't mean using the APRS-IS itself. > I'm talking about a similar distribution > system. Only I don't think it'd be wise to > send everything to everyone - just replicate > the images in the core and allow clients to > retrieve them by request. Yes, the original concept of the APRN was a local piece of software (think Igate) that monitored a local area channel (channels) and collected all SSTV live images with APRS tags on them for labeling and retrieval. Then the images were available on the WEB locally from that server via a unique URL. But also like an Igate, this APRN node forwards that packet LABEL along with the URL into a central global APRN server. So the images are kept locally for local access (Via RF or local WEB) but the links and pointers to those images are contained in a single packet that is available globally. Come to think about it, that one packet per image would not be an unnecessary burden on the existing APRS global network. SO although I initinally was thinking about a separate APRN distribution system, now I think that with just one packet per image, that we shoud consider it on the APRS network. Since each image was accepted and filed at the local APRN node with its "APRS" tag, then the images can be retrieved locally by: 1) By callsign 2) By area (by location) 3) by orientation (view west, etc) 4) by subject (fire, flood, power line, etc...) Since the URL was distributed in the same packet. > Or maybe only share pointers to images and > let everyone host what they receive. Next email will address format of that one packet: Bob, WB4APR
- Previous message: [htaprs] VC-H1
- Next message: [htaprs] VC-H1 APRN network
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the htaprs mailing list
