On Wed, 23 Oct 2013, Sergey Poziturin wrote to mark lewis:

 US>> The only thing to consider ... nodes supporting HotDogED clients 
 US>> should add the freq magic ECHOLIST in their system and 
 US>> ECHOZZZZ.ZIP to be sent. So on the supporting system the echo 
 US>> uplink lists have to be compiled and named ECHOZZZZ.LST and zip'd 
 US>> thereafter ...  =;)
 ML> is there anything wrong with sending the existing, published and 
 ML> distributed Echolist? is the above perhaps talking about something 
 ML> else other than the Echolist? something, perhaps, like the list of 
 ML> available areas (%AVAIL) from the feed's uplinks? where are other, 
 ML> unlisted, area names to be found? how is one to know of the 
 ML> existance of an area if it is not in the %AVAIL or %LIST areafix 
 ML> responses?

 SP> I prefer creating a communicating interface between hotdoged and
 SP> the node to transfer not only echo names, but also amount of
 SP> messages in the group, last message date and so on. 

quantities are available in the Echolist but they are manually maintained...
last post date is not and there's no real way to do so because of the nature
of the media...

consider this scenario: a system has problems with a corrupted tosser setup
and restores an old tosser config... that config is missing a area of
interest... systems downstream of the broken system are now cut off from those
upstream of the broken system... each system is its own pocket for the area...
where do we gather the statistics from? the broken system? one of those
upstream from it? the point's feed downstream from the broken system?

[/devil's advocate]

)\/(ark

--- FMail/Win32 1.60
 * Origin:  (1:3634/12.71)