Setting cookies in service overloader thingo

[Bluebie, Jenna]

I haven't read through all of camping yet, I only started playing with  
it seriously a few days ago, so I don't know where might be a better  
place for it. Maybe whatever it is which calls service could do the  
cookies.

it would be nice if there was a way to set cookies long term too,  
though it isn't really important and for my app, the only place I'd be  
using it is to duplicate the form filling out functionality for my  
openid login box that all modern browser's already provide.

It is really refreshing for cookies to be so simple. I have very mixed  
feelings about making them 'complete'.

If more complete cookie support were added, that would surely include  
the setting of expiry, this opens up another big change in that many  
apps set the same cookie over and over even though nothing has changed  
because they want the expiry to always be, for example, one week after  
the last page the user loaded. The framework currently doesn't make  
allowances for setting the same cookie over and over when no data has  
changed either.

Maybe it's best to stick with simple cookie support. If people really  
need much more I don't feel it unfair for them to need to hack it in  
themselves or move up to rails and the likes.

—
Jenna ”Where's my equestrian hat?” Fox

On 18/05/2008, at 2:41 AM, zimbatm wrote:

> Nice catch,
>
> cookies support never really felt complete to me. Maybe we should put
> it in a different module ?
>
> Cheers,
>  zimbatm
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list