Subj : Re: File Echos, HTick, FwdFile Question
To : Janis Kracht
From : Eric Renfro
Date : Tue Sep 08 2015 05:06 pm
Re: Re: File Echos, HTick, FwdFile Question
By: Janis Kracht to Eric Renfro on Mon Sep 07 2015 01:55 pm
JK> Hi Eric,
>>> The file your looking for is filegate.zxx and it's in the fg_worf
>>> file area.
>>> The rest I can't remember off the top of my head but looks like you
>>> just about have it.. :)
>> I did manage to find that much, and see the filegate.zxx, and yes,
>> while I'm /almost/ there, I'm not sure... what format HTick is
>> expecting. Does Htick support that zxx format? I'll be tinkering
>> around with it, trying things out, since I'm using my point node
>> internally to test against.
JK> The format used in filegate.zxx is the same format that has always been
JK> used for File Echos. Htick should import fine if I'm understanding what
JK> your asking here <g>
So, I finally got Htick setup to handle FileEcho forward requests. It lacks the
ability to %LIST them in the listing, but it does send the requester an
acknowledgement netmail to say it's been forwarded when it's validated for the
uplink.
The problem is, the htick doesn't understand the filegate.zxx format, so when
using that file as the filefixFwdFile, requests get replied back with "no
uplinks to forward". When I converted a partial of the file to the
echomail-style NA format, TAG<space>DESC, it works just fine.
With that said.. Would it be reasonable to request that the filegate.zxx be
published in the same format as echomail.na files, so that automation could be
easily obtained for systems like this? Yes, I could make a tool to convert the
file myself, and likely I will, but that will take some time to write that
tool, make it extract from the fg_worf archives as they come in, process the
conversion, drop it down in the place it needs to be.
An alternative would be to write some tool to convert it one time for the
publishing end, and just distribute it like that simaltaneously. :)
