Re: flexfax: Design for a portable Java hylafax clients: i want your opinions, please!

[Arne Hueggenberg <zalaster@nef.wh.uni-dortmund.de>]

Am Don, 04 Mai 2000 schrieben Sie:
> Hello to all hylafax users.
> 
> I am currently developing a java hylfax client, there are some topics i
> am thinking about, maybe you can give me your opinions:
> 
> 1. is java 2 widely availabe on your (client) platforms?
>    or is it supposed to become availbe in the near future?

yes and yes

> 2. What is your prefered procedure for sending a fax?
> 
>    a1. redmon: capture the printout of an application on the client side
>        and let the hylafax client process it: e.g. ask user for fax.nr.
>        and the hand it to the hylafax server directly.
> 
>        advantage: faster than a2
>        disadvantage: - firewall must be opened for ports use by hfaxd
>                      - if you want access for remote users you must open
> hfaxd ports
>                        to the public.

this would be my preferred mode, as it would be transparent for the user
"simply print your doc to the "fax" :-)

as it is possible to restrict acess to ports by source ip i dont see that big a
problem with this

>    a2: same as a1, but client will send an eMail to some dedicated process
> on the server
> 
>        advantage: - no firewall problem if eMail is allowed
>                   - remote users can send faxes as if they where at the office
>        disadvantage: slower than a1

i dont like this due to the "dedicated process on the server, the vulnerability
here is imo far greater than with a)
another process wich can die etc.
and remote users can use a) as if they were at the office too :-)  

>    b. printfax/repsond: capture the printout on the server side, make a
> "callback" to the client to get fax.nr. etc.
> 
>       advantage: protocoll between client server can be easily adopted by
> other developers
>       disadvantage: - another port must be opened for client server
>                                   communications

this would be another possibility, user transparent like a)
but i dont really see an compelling argument for this, the current protocol is
established, has mechanisms for transferring the relevant stuff, and is already
implemented on the server side.
Why do it again?

> 
> 
> Currently it is usual that a client transfers a PS file to the server for
> sending.
> Receiving faxes are stored in TIFF.
> -> viewers for 2 different formats are needed on the client.
>
> Does anybody know a free printer driver which can produce TIFF files from
> the printout of an application?
> Can hylafax convert an arbitrary TIFF file to a TIFF file suitable for fax
> transmission?
> 
> TIA for you opinions!
> 
> Bernd

Arne