Michael wrote:
> On Sat, 25 Apr 2009 16:59:48 you wrote:
>   
>> I probably have not understood what exactly you need, however I think you
>> can try these options
>>
>> 1 . the batch file / call file gets deleted if the number of retries are
>> ended so you can try changing number of retries
>> 2.  an action can be defined in the dialplan to remove the file
>>     
>
> Problem is that will indiscriminately remove all batch files, whether they 
> have expired their retry times or not. This is why I would rather let TXFax() 
> do the work of deleting expired batch files.
>
>   
>> 3.  run external script to delete the files, based upon file creation time
>> / modifcation time.
>>     
>
> Same answer again.
>
> What I fail to understand is why the person writing the software didn't code 
> a 
> spooling mechanism in to it. This defies logic and is why I am left to write 
> my own.
>   
Well the basic reason is that the free software user base sucks. Rather 
than contribute a solution people would rather whine that the whole 
world hasn't been given to them for free. After several years of huge 
numbers of people facing the same issue a clean solution has not made 
its way into the code base, because nobody contributed one. rxfax and 
txfax were never intended to be apps. They were just my little test 
programs top exercise the FAX engine. I navely thought someone would 
take an interest in making a realyl nice app, but nobody has to date. 
Few people even bother reporting bugs, so problems large number of 
people hit stay in all sorts of packages for years, because nobody 
bothered to tell anyone who might have been inclines to fix them.
> If someone submits 100 fax jobs to CW, it tries to send all 100 at once...
>   
Steve

_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users

Reply via email to