"notify" and converted tiff availability

"[email protected]" <[email protected]>
Newsgroups gmane.comp.telephony.fax.hylafax.devel
Message-ID <15307831.8291261412760638.JavaMail.defaultUser@defaultHost>
Hello,
when I send a fax, I'd like to be able to confirm not only that it has
been sent 
successfully but also what exactly has been sent. There seem to
be no easy way to do this with 
current hylafax, unless I'm missing
something.
My understanding is that, when a fax is queued, 
hylafax converts it to
tiff and adds "fax:" lines in the qfile pointing to the generated tiff

files. After successfully sending the fax (that is, the generated
TIFFs are transmitted), notify is 
called with reason "done", but at
that point the "fax:" lines have already been removed, together 
with
the generated TIFFs.
So there is no way to see what exactly has been sent, nor to generate
a 
report showing that. Eventually it is possible to generate a report
showing what has been submitted 
(the original document, before hylafax
converted it to tiff, which is still available and listed in 
the qfile
when "notify done" is called). I think this is not good enough, since
during the 
conversion there are a number of things that can make the
converted tiff unreadable (mapped fonts, 
dithering, color rendition,
uncaught errors, etc...).
Is it possible to delay the removal of the 
"fax:" lines and generated
tiff files until AFTER "notify done" is called?
Also, it might be useful 
to add another event upon which
"notify" is called, which is "document converted", meaning that the

transmission tiff has been generated and the qfile updated with its
path). So that a client 
application can let the user check what is being
transmitted even before it is actually 
transmitted.
Regards,
LB




____________________ HylaFAX(tm) Developers Mailing List ____________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe [email protected] < /dev/null
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.