+ # the spot at the same time (velocity factor of the atmosphere and network delays
+ # carefully (not) taken into account :-)
+
+ # Note, there is no intelligence here, but there are clearly basic heuristics that could
+ # be applied at this point that reject (more likely rewrite) the call of a busted spot that would
+ # useful for a zonal hotspot requirement from the cluster node.
+
+ # In reality, this mechanism would be incorporated within the cluster code, utilising the dxqsl database,
+ # and other resources in DXSpider, thus creating a zone map for an emitted spot. This is then passed through the
+ # normal "to-user" spot system (where normal spots are sent to be displayed per user) and then be
+ # processed through the normal, per user, spot filtering system - like a regular spot.
+
+ # The key to this is deducing the true callsign by "majority voting" (the greater the number of spotters
+ # the more effective this is) together with some lexical analsys probably in conjuction with DXSpider
+ # data sources (for singleton spots) to then generate a "centre" from and to zone (whatever that will mean if it isn't the usual one)
+ # and some heuristical "Kwalitee" rating given distance from the zone centres of spotter, recipient user
+ # and spotted. A map can be generated once per user and spotter as they are essentially mostly static.
+ # The spotted will only get a coarse position unless other info is available. Programs that parse
+ # DX bulletins and the online data online databases could be be used and then cached.
+
+ # Obviously users have to opt in to receiving RBN spots and other users will simply be passed over and
+ # ignored.
+
+ # Clearly this will only work in the 'mojo' branch of DXSpider where it is possible to pass off external
+ # data requests to ephemeral or semi resident forked processes that do any grunt work and the main
+ # process to just the standard "message passing" which has been shown to be able to sustain over 5000
+ # per second (limited by the test program's output and network speed, rather than DXSpider's handling).
+