Thanks all for your answers.
When I use twisted ssl by commenting the 8080 server and uncommenting the ssl
server it seems to work. But I can't seem to be able to use apache as a proxy.
Thanks again,
Stéphane
- Message d'origine
De : Philipp von Weitershausen <[EMAIL PROTECTED]>
À
Zope Corporation is happy to announce a number of newly open-sourced
packages. All are in use, in development, or both.
We release these packages in the strong hope that others will
contribute to them, from maintenance through extension to
refactoring. The maintainers are effectively "zop
Gary Poster wrote:
Zope Corporation is happy to announce a number of newly open-sourced
packages. All are in use, in development, or both.
[snip long list]
Awesome! And thanks for this announcement! And here Infrae's with only 3
hurry packages last year - I feel totally inadequate. :)
Echoi
On Aug 24, 2006, at 12:14 PM, Martijn Faassen wrote:
Gary Poster wrote:
Zope Corporation is happy to announce a number of newly open-
sourced packages. All are in use, in development, or both.
[snip long list]
Awesome! And thanks for this announcement! And here Infrae's with
only 3 hurry
Objects containing a string attribute that have been 'copied/pasted' from some
other application such as MS Office suite or email will raise an encoding error
when attempting to be viewed in a Skin. The encoding issue is not a
problem however when being viewed in the ZMI. Does anyone h
Hi Keith,
I assume you are viewing the ZMI with the Rotterdam skin which contains
the following meta tag (as does the Boston skin). Does your Skin also
define the same charset?
This may or may not be the cause of your problem.
Regards,
Darryl
On Thu, 2006-08-24 at 14:56 -0700, Keith Bolton wr
On Thursday 24 August 2006 16:54, Benji York wrote:
> Stephan's ZSCP proposal suggests using the package name "z3c" for
> "community" packages. IOW, packages that aren't part of a larger
> collection like lovely.*, zc.*, etc.. There are currently several z3c
> packages in existence.
>
> The zope3
On 8/24/06, Benji York <[EMAIL PROTECTED]> wrote:
If "zc" were to become "zope community", I'd be *totally* for it (but I
don't speak for ZC here, so that may not be cool with others, like say
Jim). We'd either keep using "zc" under the new meaning, or switch to
something else.
"z3c" clearly s
Stephan's ZSCP proposal suggests using the package name "z3c" for
"community" packages. IOW, packages that aren't part of a larger
collection like lovely.*, zc.*, etc.. There are currently several z3c
packages in existence.
The zope3.org packages currently use the package name "zorg". I
pe
Benji York wrote:
> Stephan's ZSCP proposal suggests using the package name "z3c" for
> "community" packages. IOW, packages that aren't part of a larger
> collection like lovely.*, zc.*, etc.. There are currently several z3c
> packages in existence.
>
> The zope3.org packages currently use the p
On Thursday 24 August 2006 16:57, Philipp von Weitershausen wrote:
> > (In fairness, I'll note that Stephan likes z3c better, and that name is
> > already in semi-wide-spread use).
>
> Afaik, nothing has been released yet. Plus, changing the namesapce
> shouldn't be that hard, simple search'n'repla
Stephan Richter wrote:
> On Thursday 24 August 2006 16:54, Benji York wrote:
>> Stephan's ZSCP proposal suggests using the package name "z3c" for
>> "community" packages. IOW, packages that aren't part of a larger
>> collection like lovely.*, zc.*, etc.. There are currently several z3c
>> package
Stephan Richter wrote:
Right, thus I am clearly -1. :-) (Wow, now I do not even have to argue myself
anymore. ;-)
:)
Note that we spent a lot of time coming up with this name and pretty much all
the contributors to the namespace were involved in the discussion.
Sorry.
Zope Corp decided to
13 matches
Mail list logo
