![]() |
Nicola Murino wrote:
I see a patch for hylafax 4.1.5 on list archives,
I'm not sure to what you refer. hylalog? I've never used it.
To-date I've not had a customer approach me about needing MySQL integration with HylaFAX. (I do support many installations of open-source HylaFAX for businesses, so I don't think that every enterprise needs this feature.)This is right, only some enterprise need database support, you can share incoming fax by samba and you can print every incoming fax,
fax unix - n n - 1 pipe flags= user=fax argv=/usr/bin/faxmail -d -s -n ${user}
if isn't a commercial question and if as you say is simple to add Mysql calls to hylafax code why you don't include db support in main hylafax tree?
Again, for my part I've just never had a customer approach me about doing that work, and it really hasn't been something that I've been desireous to pursue in my hobby-time, instead having devoted most of that time to getting Class 1 protocol rock-solid and adding protocol features that do benefit my customer base.
I think db make more simple query and search. Database support make also more simple build web interfaces. I think this features can improve hylafax, however this is only my opinion.
I do not disagree.
You are right LDAP is for client authentication and not for store fax information
I search on the web and I find also some patch from gofax to add ldap support to hylafax. So also gofax guys think some sort of db supportis important for hylafax.
You'd have to provide me the reference to say for certain, but I think that the LDAP support was for client authentication purposes. We've since accomodated LDAP authentication via PAM. Again, I do not disagree that this things are important.
____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*