You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rivet-dev@tcl.apache.org by "GoMp @ tcl.no" <Go...@tcl.no> on 2004/10/04 21:59:19 UTC

Rivet cookies vs mod_dtcl cookies

When I'm setting cookies containing spaces etc in Rivet I get the followin
message:

value may not contain semicolons, spaces, or tabs
    while executing
    invoked from within

This did NOT occur in MOD_DTCL and was, as I see it, a LOT better since I
depend a lot upon the info from the cookies. This is also a result of the
poorly documented session package that is merebly a substitute for my use of
the cookies. Only way around it for me now is to map spaces into \xFF or
something and go at it that way. I hope that a solution for this "problem"
arrives in a short amount of time.

Sincerely,
    GoMp
    www.tcl.no
    www.g0mp.org


---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org


Re: Rivet cookies vs mod_dtcl cookies

Posted by "GoMp @ tcl.no" <Go...@tcl.no>.
If I understand you correctly, then you're talking about mapping as well.
Changing for instance " " to "." or something. And yes, this is a solution,
but my point is that this wasn't necessary in mod_dtcl. And if Rivet is the
new mod_dtcl, then I would expect Rivet to be superior to mod_dtcl. And it
also seems to be placed there for a reason, and that's what I can't figure
out. Why shouldn't we be able to store spaces etc?

----- Original Message -----
From: "Damon Courtney" <dc...@hmssoftware.com>
To: "GoMp @ tcl.no" <Go...@tcl.no>
Cc: <ri...@tcl.apache.org>
Sent: Monday, October 04, 2004 10:10 PM
Subject: Re: Rivet cookies vs mod_dtcl cookies


> GoMp @ tcl.no wrote:
>
> >When I'm setting cookies containing spaces etc in Rivet I get the
followin
> >message:
> >
> >value may not contain semicolons, spaces, or tabs
> >    while executing
> >    invoked from within
> >
> >This did NOT occur in MOD_DTCL and was, as I see it, a LOT better since I
> >depend a lot upon the info from the cookies. This is also a result of the
> >poorly documented session package that is merebly a substitute for my use
of
> >the cookies. Only way around it for me now is to map spaces into \xFF or
> >something and go at it that way. I hope that a solution for this
"problem"
> >arrives in a short amount of time.
> >
> >
>     I usually just use a session key in cookies and store any relevant
> data in a table somewhere with the cookie key as a reference.  This has
> the added benefit of not storing any real data in the client.  If you're
> really into storing arbitrary data in the client, I'd just escape the
> string.  IE:
>
> cookie set mycookie [escape_string $myData]
>
> ...
>
> set my data [unescape_string [cookie get mycookie]]
>
>     I don't have the code in front of me, but that should be about right.
>
> Damon
>


---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org


Re: Rivet cookies vs mod_dtcl cookies

Posted by Damon Courtney <dc...@hmssoftware.com>.
GoMp @ tcl.no wrote:

>When I'm setting cookies containing spaces etc in Rivet I get the followin
>message:
>
>value may not contain semicolons, spaces, or tabs
>    while executing
>    invoked from within
>
>This did NOT occur in MOD_DTCL and was, as I see it, a LOT better since I
>depend a lot upon the info from the cookies. This is also a result of the
>poorly documented session package that is merebly a substitute for my use of
>the cookies. Only way around it for me now is to map spaces into \xFF or
>something and go at it that way. I hope that a solution for this "problem"
>arrives in a short amount of time.
>  
>
    I usually just use a session key in cookies and store any relevant 
data in a table somewhere with the cookie key as a reference.  This has 
the added benefit of not storing any real data in the client.  If you're 
really into storing arbitrary data in the client, I'd just escape the 
string.  IE:

cookie set mycookie [escape_string $myData]

...

set my data [unescape_string [cookie get mycookie]]

    I don't have the code in front of me, but that should be about right.

Damon


---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org