Hi all,
Just wanted to say thanks to everybody who answered. After using H::T
for less than a week I can already say - it is great, I love it! :-)
Thanks again for all your answers,
Offer Kaye
---
This SF.net email is sponsored by: SF.net Giv
[EMAIL PROTECTED]:
Thilo Planz wrote:
> Everything you send or receive via https is encryted.
> This even includes the HTTP headers, which is why name-based virtual
> hosting does not work with https.
Thanks for your reply. :-)
Okay.
> Depending on how paranoid you are you can also set the "se
Kenneth Gonsalves wrote:
hi,
i've been playing with H::T to produce formatted plain text reports in an
Xwindows based application. Seems to be much more flexible than using perl
Formats. So i dont go reinventing the wheel can anyone point me to some tips
and tricks to achieve things like centeri
On Wednesday, October 15, 2003, at 02:49 AM, David Christensen wrote:
..
1.) Establish an SSL connection
2.) Require the user to indentify himself (username and password)
3.) Check against some kind of user database
4.) Create a unique session ID number which can not easily guessed
by other
On Wed, Oct 15, 2003 at 05:44:17PM +0530, Kenneth Gonsalves wrote:
>i've been playing with H::T to produce formatted plain text reports in an
>Xwindows based application. Seems to be much more flexible than using perl
>Formats. So i dont go reinventing the wheel can anyone point me to some tips
hi,
i've been playing with H::T to produce formatted plain text reports in an
Xwindows based application. Seems to be much more flexible than using perl
Formats. So i dont go reinventing the wheel can anyone point me to some tips
and tricks to achieve things like centering, right or left justifi
[EMAIL PROTECTED]:
Bär, Sebastian wrote:
> Most session tracking software use the same approach:
Thanks for the reply. :-)
> 1.) Establish an SSL connection
> 2.) Require the user to indentify himself (username and password)
> 3.) Check against some kind of user database
> 4.) Create a unique
Hi David.
Most session tracking software use the same approach:
1.) Establish an SSL connection
2.) Require the user to indentify himself (username and password)
3.) Check against some kind of user database
4.) Create a unique session ID number which can not easily guessed
by others
5.) Store
