[Seaside-dev] Fwd: [Seaside Issues] Issue 542 in seaside: implement Strict Transport Security

[Avi Shefi]

Hi,
Naming conventions are no problem. You use
Seaside-Core-<initials>.<number>.mcz, right? so the next version using my
will be: Seaside-Core-<initials>.661.mcz if I'm not mistaken.

About a configurable filter - Where can I learn about building a
configurable filter? Can you give an example for this in Seaside core?


Thanks.

---------- Forwarded message ----------
From: <seaside at googlecode.com>
Date: Sun, Sep 5, 2010 at 12:37 PM
Subject: Re: [Seaside Issues] Issue 542 in seaside: implement Strict
Transport Security
To: issues at lists.seaside.st



Comment #4 on issue 542 by philippe.marschall: implement Strict Transport
Security

http://code.google.com/p/seaside/issues/detail?id=542

That didn't really work, it's empty and the file naming is a bit different
from what we usually use. In general I would recommend first getting
familiar with Smalltalk and Smalltalk development before contributing to
Seaside. There is a lot to learn there before digging into the core of a
framework that has evolved over several years.

Looking at the spec again I feel that a configurable filter is needed as
well.





_______________________________________________
issues mailing list
To unsubscribe, email issues-leave at lists.seaside.st
http://lists.seaside.st/listinfo/issues
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20100911/6820563e/attachment.htm