Re: Contribution question

--Apple-Mail-18-804039203
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=ISO-8859-1;
	format=flowed

Hi Michael,

Use Robert's setup framework to provide a settings area for the user.  =
=20
I'd prefer that you provide a rudimentary interface in is area rather=20
than point to a file, which makes it too hard for a large fraction of=20
our users.

Best to saved the settings in our existing preferences file, rather=20
than a separate file.  This needs to work seamlessly cross platform and=20
this is the best way to ensure this.  Also, you can use the Prefs=20
interface for parsing and saving these options so you won't have to=20
write your own.

-dean



On Wednesday, February 19, 2003, at 11:17  AM, Metzger, Michael wrote:

> Hi All,
> =A0
> =A0=A0 I've implemented a simple IP based access control scheme into the=
=20
> HTTP and CLI servers.=A0 This will initially accept the connection as=20
> normal, check the IP against the valid options listed, and either=20
> allow the connection to continue accordingly or kill the socket before=20
> continuing.=A0 This all works fine at this point, but as I've just=20
> started hacking on this code, I have a few organizational questions=20
> about where to put things:
> =A0
> 1) I put the options to enable this feature and the name of the file=20
> containing this in Prefs.pm.=A0 Is this correct?
> =A0
> 2) Considering that this IP check is for both CLI and HTTP, I put the=20
> actual parsing/writing (of the allowedhosts file) and validating=20
> functions in Misc.pm.=A0 Is there a better network-oriented module to=20
> put these in?=A0
> =A0
> Thanks!
> =A0
> Mike Metzger
> =A0
>
<image.tiff>
>
>
> To unsubscribe from this group, send an email to:
> [email protected]
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
--Apple-Mail-18-804039203
Content-Transfer-Encoding: quoted-printable
Content-Type: text/enriched;
	charset=ISO-8859-1

Hi Michael,


Use Robert's setup framework to provide a settings area for the user. =20=

I'd prefer that you provide a rudimentary interface in is area rather
than point to a file, which makes it too hard for a large fraction of
our users.


Best to saved the settings in our existing preferences file, rather
than a separate file.  This needs to work seamlessly cross platform
and this is the best way to ensure this.  Also, you can use the Prefs
interface for parsing and saving these options so you won't have to
write your own.


-dean




On Wednesday, February 19, 2003, at 11:17  AM, Metzger, Michael wrote:


<excerpt><fontfamily><param>Arial</param>Hi All,</fontfamily>

=A0

<fontfamily><param>Arial</param>=A0=A0 I've implemented a simple IP =
based
access control scheme into the HTTP and CLI servers.=A0 This will
initially accept the connection as normal, check the IP against the
valid options listed, and either allow the connection to continue
accordingly or kill the socket before continuing.=A0 This all works fine
at this point, but as I've just started hacking on this code, I have a
few organizational questions about where to put things:</fontfamily>

=A0

<fontfamily><param>Arial</param>1) I put the options to enable this
feature and the name of the file containing this in Prefs.pm.=A0 Is this
correct?</fontfamily>

=A0

<fontfamily><param>Arial</param>2) Considering that this IP check is
for both CLI and HTTP, I put the actual parsing/writing (of the
allowedhosts file) and validating functions in Misc.pm.=A0 Is there a
better network-oriented module to put these in?=A0</fontfamily>

=A0

<fontfamily><param>Arial</param>Thanks!</fontfamily>

=A0

<fontfamily><param>Arial</param>Mike Metzger</fontfamily>

=A0


</excerpt><<image.tiff>

<excerpt>


To unsubscribe from this group, send an email to:

[email protected]




Your use of Yahoo! Groups is subject to the
<underline><color><param>1999,1999,FFFF</param>Yahoo! Terms of
Service</color></underline>.</excerpt>=

--Apple-Mail-18-804039203--