> This is how the HTTP 1/1 specification requires it to be.
> Your browser follows this spec.
Dieter,
I understand the HTTP spec... but ZOPE does not work that way.
I can use methods which require roles above where I logged in. The
methods used for returning the roles themselves do not
> > > The SignalHandler.py class is not used by zdaemon itself; perhaps it
> > > can be moved into the Signals package?
>
> Will do.
Done.
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Zope-Dev maillist - [EMAIL PROTECTED]
http:/
> I don't know where you would expect a patch to be found, but in this
> particular case the Zope Collector is a good place to look:
>
> http://collector.zope.org/Zope/597
>
> Use the collector, Luke! ;-)
Um, that's not a patch. Can you attach a context or unified diff to
the collector item?
>
> I must've missed the start of this thread (I only just signed up for
> this list). I didn't see any patch -- I thought it was just a gripe
> about ZCTextIndex. Of course patches are welcome -- where can I find
> this particular patch?
Hi Guido!
I don't know where you would expect a patch to b
> I think all these things are reasonable things to do...
>
> Guido van Rossum wrote:
> > The zdaemon package contains a bunch of dead wood, or "decoys", as Jim
> > would call it, that I'd like to remove. AFAICT, Heartbeat.py is not
> > used anywhere. At least not in the Zope sources -- maybe th
> "kt" == kapil thangavelu <[EMAIL PROTECTED]> writes:
>> e.g. BerkeleyStorage or OracleStorage.
kt> is there a useable undoable storage?
I think you meant "useable non-undoable storage", right?
If so, then I believe that ZODB 3.2 will have a such a useable
storage. We've had some
I think all these things are reasonable things to do...
Guido van Rossum wrote:
The zdaemon package contains a bunch of dead wood, or "decoys", as Jim
would call it, that I'd like to remove. AFAICT, Heartbeat.py is not
used anywhere. At least not in the Zope sources -- maybe there are
outside u
> >>The problem seems to be that ZCTextIndex indeed does not do the
> >>splitting "right" if German Umlauts are used. There is no option for
> >>"Unicode-aware splitter". Instead of a Vocabulary it uses a
> >>Lexicon, which just offers two options: "HTML aware splitter" and
> >>"Whitespace splitte
Guido van Rossum wrote:
The problem seems to be that ZCTextIndex indeed does not do the
splitting "right" if German Umlauts are used. There is no option for
"Unicode-aware splitter". Instead of a Vocabulary it uses a
Lexicon, which just offers two options: "HTML aware splitter" and
"Whitespace sp
> The problem seems to be that ZCTextIndex indeed does not do the
> splitting "right" if German Umlauts are used. There is no option for
> "Unicode-aware splitter". Instead of a Vocabulary it uses a
> Lexicon, which just offers two options: "HTML aware splitter" and
> "Whitespace splitter". I have
Hi!
> Please note that former Zope versions already include a dedicated
> unicode-aware
> splitter that is already usable with the old TextIndex and maybe with
> ZCTextIndex.
> TextIndexNG resolves all these issues by doing the complete internal
> processing by
> converting the data into unicode.
11 matches
Mail list logo
