thanks, guys.
Dylan Vanderhoof wrote:
http://catalyst.perl.org/calendar/2007
-Original Message-
From: Fayland Lam [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 02, 2007 5:01 PM
To: Catalyst@lists.scsys.co.uk
Subject: [Catalyst] any plan for advent calendar?
2008 Catalyst Advent C
On 3 Dec 2007, at 12:00, Fayland Lam wrote:
2008 Catalyst Advent Calendar?
The 2007 one is up at http://catalystframework.org/calendar/2007.
it's a bit early to start thinking abuot 2008 at this stage ;-)
___
List: Catalyst@lists.scsys.co.uk
L
http://catalyst.perl.org/calendar/2007
> -Original Message-
> From: Fayland Lam [mailto:[EMAIL PROTECTED]
> Sent: Sunday, December 02, 2007 5:01 PM
> To: Catalyst@lists.scsys.co.uk
> Subject: [Catalyst] any plan for advent calendar?
>
>
> 2008 Catalyst Advent Calendar?
>
> --
> Fayland Lam
2008 Catalyst Advent Calendar?
--
Fayland Lam // http://www.fayland.org/
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
Dev
I'm hoping I've got something configured wrong, but session and cookie
handling still seem to have a problems.
This has been an ongoing problem. I'm all up-to-date with Catalyst
and Plugins. What I see, once in a while is a state where the browser
returns a cookie. The returned session id is in
On Dec 2, 2007 8:33 AM, Ian Docherty <[EMAIL PROTECTED]> wrote:
> Zbigniew Lukasiak wrote:
>
> On Dec 2, 2007 12:38 PM, Ian Docherty <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
> wrote:
>
>
> Zbyszek
> You have to remember that Siemens are responsible for ensuring the
> stability of the public faci
Zbigniew Lukasiak wrote:
On Dec 2, 2007 12:38 PM, Ian Docherty <[EMAIL PROTECTED]> wrote:
Zbyszek
You have to remember that Siemens are responsible for ensuring the
stability of the public facing infrastructure.
This makes it important not to introduce new modules, or upgrade
existing modules
On Sun, 2007-12-02 at 16:41 +0200, Angel Kolev wrote:
> Hi again :) I found a solution i think. With Encode::Detect i can do:
> use Encode;
> require Encode::Detect;
> my $utf8 = decode("Detect", $data);
Looks like this module uses Mozilla's encoding detector, which does a
pretty good job i
Hi again :) I found a sollution i think. With Encode::Detect i can do:
use Encode;
require Encode::Detect;
my $utf8 = decode("Detect", $data);
And for now it works!
More:
use Encode::Detect::Detector;
my $charset = detect($octets);
It prints sended charset (eg windows-1251,UTF-8,KOI8
On Dec 2, 2007 12:38 PM, Ian Docherty <[EMAIL PROTECTED]> wrote:
> Zbyszek
> You have to remember that Siemens are responsible for ensuring the
> stability of the public facing infrastructure.
> This makes it important not to introduce new modules, or upgrade
> existing modules, without an extensiv
On Sun, 2007-12-02 at 12:38 +, Ian Docherty wrote:
> You have to remember that Siemens are responsible for ensuring the
> stability of the public facing infrastructure.
Why do people think that code they write in-house is more stable than
code written by a community of experts and used by th
A single monolithic par might be in order /cackle
> You have to remember that Siemens are responsible for ensuring the
> stability of the public facing infrastructure.
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mai
Zbyszek
You have to remember that Siemens are responsible for ensuring the
stability of the public facing infrastructure.
This makes it important not to introduce new modules, or upgrade
existing modules, without an extensive
testing period to make sure it works with all existing applications. T
Is it possible that we go to the root of that and ask Siemens about
their policy for whitelisting modules? I can understand that they
want to keep some control over this - but if we new what process they
use for that and what criteria - then perhaps we could help them in
some way? In the age of s
Hi, again. I have problem with my utf8 again. When i send request to my
catalyst app from PC with encoding cp1251, i must use:
require Encode;
$string = Encode::decode('cp1251,$string');
to make it utf8 and put in mysql. How i can know what encoding the user will
use? Is there any universal solutio
15 matches
Mail list logo