Re: [hylafax-users] General question

[Marcin Giedz <marcin.giedz@xxxxxxxxxxxx>]

Lee Howard napisał(a):
> Marcin Giedz wrote:
>
> > Till now I've also made some small changes for Hylafax (LDAP 
> > authentication + privileges) - rather for internal use but it works.
>
>
> I think that you sent those patches to the list once.  (?)  Remind me.  
Yes indeed ;)
> Is direct LDAP auth that much better/easier than PAM-LDAP auth?
No it's not..... but I simply needed such feature so it's been written then
> > However in my daily work I have not only Hylafax working - also 
> > CapiforHylafax + CapiRCVD. Together they create REALLY powerfull 
> > tool. I've almost always been wondering what is the reason to NOT 
> > include CAPI into Hylafax?
>
>
> Firstly, CAPI4HylaFAX is licensed GPL... so it makes it difficult to 
> merge the two.  Secondly, to my knowledge none of the CAPI4HylaFAX 
> developers (only AVM employees?) participate in HylaFAX development at 
> all... so that makes it hard to coordinate work (like how CAPI4HylaFAX 
> doesn't support batching).
So the main reason except GPL is that No-ONE was/is willing to start 
such support? Hmmm.... I can't say "Here I am" but I simply need to 
calculate my time....but it's still possible to start such thing.
> > OK as I mentioned we have Hylafax + CAPIforHylafax but they are 
> > rather two separated programs. Is there any obstacle regarding such 
> > connection? Hylafax works normal with lots of modems, why shouldn't 
> > it work with CAPI/ISDN modems directly?
>
>
> Sam started HylaFAX (FlexFAX at the time) because, "I saw a fax modem 
> sitting unused in a colleague's office at SGI one day."  And it went 
> from there.  That modem used the Hayes AT-command set, and so HylaFAX 
> began by supporting that DCE-DTE communication medium "ClassModem".  
> Certainly HylaFAX could have a proposed "CAPIModem" driver built-in 
> directly (none of that c2faxrecv/c2faxsend stuff), but it's not 
> happened yet... that takes some code work.
Can I see it? Is it already available with current Hylafax code?
> The easiest path to getting it all integrated would be to get AVM to 
> give license to HylaFAX to integrate and incorporate CAPI4HylaFAX code 
> into the HylaFAX codebase.  With that it should be a fairly 
> straight-forward process to create the "CAPIModem" driver/interface.
Can be difficult ..... but then again....the more support you have the 
more cards (AVM) you can sell ;)
> Otherwise we'd need to have someone with the CAPI spec and some 
> hardware take the time to reconstruct much of what CAPI4HylaFAX has 
> already done.  And in my experience that just doesn't happen without 
> the right kind of motivation and the right kind of person/company.
Hmmm.... this is no so bad idea I think... Let me think about this 
more.... I'm sure we'll be in touch regarding this "thing".

> Lee.
Marcin
> ____________________ 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*

begin:vcard
fn:Marcin Giedz
n:Giedz;Marcin
org:AltVision Group;Network & New Technologies
adr:;;Polna 11;Warszawa;;00-633;Polska
email;internet:marcin.giedz@xxxxxxxxxxxx
title:Application Engineer
url:http://www.altvision.pl
version:2.1
end:vcard