On 8/31/05, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
> HTML4 mode exists because
...
> - it enforces some HTML document type (as mentioned before); no idea why
> it does that
I'm just guessing you're referring to its understanding of the allowed
nesting structures. This is done so tha
On Aug 31, 2005, at 12:07 PM, David Huttleston Jr wrote:
...
But, I'm fuzzy on how the zodb prevents inconsistent reads.
...
Hi David. A quick answer is that the ZODB implements optimistic
multi-version concurrency control, similar to the default PostgreSQL
behavior. This link describes
On Wed, 2005-08-31 at 10:07 -0400, Gary Poster wrote:
> >> I'm interested in contemplating RDF as a full catalog solution for
> >> Zope, at least as a thought experiment.
Great!
> > Note that the use of bound variables also removes the need for brains.
>
> We actually don't have catalog brain
Jim Fulton wrote:
> Jean-Marc Orliaguet wrote:
> ...
>
>> Also this is as bad as storing browser view related attributes in a
>> content class - otherwise we are back to the Zope2 old days, where every
>> possible attribute was stored on the objects themselves.
>
>
> There are advantages in storin
Jean-Marc Orliaguet wrote:
Janko Hauser wrote:
Am 31.08.2005 um 10:25 schrieb Jean-Marc Orliaguet:
Hi !
I have been thinking about Jim's question: "why do you need
relations?".
Some obvious answers came first others emerged later on, now I think
that most of them are emerged, so I'll try
A change in style, if applied everywhere can lead to massive
code changes. This can have serious downsides. If people
are working on branches, where most new work should be done,
then merging is made more difficult. People who read the checkins
have a lot of extra code to review for a small be
Jean-Marc Orliaguet wrote:
...
- this portlet uses this style
not for a *class* of portlets, but for *instances* of classes. Adapters
connect interfaces, not instances.
Then why not just store the style in the portlet?
Again you are making the assumption that a portlet *has* a style. If th
I've added a proposal for Zope 3.2. Read at
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/ResourceLibrary.
WARNING: zope.org exhibiting some serious caching strangeness, so please
comment on the list instead of the wiki.
--
Benji York
Senior Software Engineer
Zope Corporati
On Wed, Aug 31, 2005 at 10:46:34AM -0400, Stephan Richter wrote:
| On Wednesday 31 August 2005 10:05, Julien Anguenot wrote:
| > > Don't forget that IE will then have an insane tendency to render the
| > > pages wrong. I don't recall all of the details, but it was something
| > > like if the docum
Hello:
Potentially stupid question: is a query that spans multiple catalogs
analogous to a relational query that spans multiple tables?
A relational query that spans multiple tables is analyzed by the query
optimizer to make maximal use of indices.
One can also optionally pass in "hints" to
I'm exploring moving our job queue system into z3. But, I'm running
into a conceptual problem.
As I envision it, I'd have three zope zeo clients working to get the job
done. One is the queue manager taking submissions and reporting on the
status of current jobs. Another is a queue worker which
Hello Stephan,
Sorry, I'm a newbie regarding that. As I checked there is a
zope.publisher.xmlrpc.premarshal_dispatch_table dict, but this is for
the response. The request is handled 'directly' by xmlrpclib
self._args, function = xmlrpclib.loads(self._body_instream.read())
Can you please give a hin
On Aug 31, 2005, at 10:46 AM, Stephan Richter wrote:
On Wednesday 31 August 2005 10:05, Julien Anguenot wrote:
Don't forget that IE will then have an insane tendency to render the
pages wrong. I don't recall all of the details, but it was
something
like if the document began with IE woul
On Aug 31, 2005, at 5:41 AM, Martijn Faassen wrote:
Gary Poster wrote:
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be
missing in zc.catalog. A
On Wednesday 31 August 2005 10:05, Julien Anguenot wrote:
> > Don't forget that IE will then have an insane tendency to render the
> > pages wrong. I don't recall all of the details, but it was something
> > like if the document began with IE would switch to "quirks
> > mode" and do funny things
Julien Anguenot wrote:
If you change the doctype declaration with the xml header and add the
xmlns declaration for tal, metal and i18n then everything's fine after.
See for instance the navigation macros :
http://svn.zope.org/Zope3/trunk/src/zope/app/rotterdam/navigation_m
On Aug 30, 2005, at 11:46 AM, Michel Pelletier wrote:
On Mon, 2005-08-29 at 23:24 -0400, Gary Poster wrote:
Right. Well in this case we would provide just a very simple
interface
facade that had no effect when run in an environment with no
zope.interface (ie, catch the ImportError, null-out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derrick Hudson wrote:
> On Wed, Aug 31, 2005 at 03:54:45PM +0200, Philipp von Weitershausen wrote:
> | Julien Anguenot wrote:
> [...]
>
> | > If you change the header like this then it can be succesfully included :
> | >
> | >
> | > http://www.w3.or
On Wed, Aug 31, 2005 at 02:48:11PM +0200, Philipp von Weitershausen wrote:
[...]
| PageTemplates know two different modes, HTML4 mode and XML mode:
[...]
| So, instead of proposing to radically get rid of HTML4 mode, I propose this:
|
| - XML mode of ZPT becomes the standard mode.
|
| - We keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
> Julien Anguenot wrote:
>
>>Ok the problem is the doctype declaration on top of the macro files that
>>force the tal interpretor to enter html mode and as far as I understand
>>you can't have mix moded macros.
>
>
>
On Wed, Aug 31, 2005 at 03:54:45PM +0200, Philipp von Weitershausen wrote:
| Julien Anguenot wrote:
[...]
| > If you change the header like this then it can be succesfully included :
| >
| >
| > http://www.w3.org/1999/xhtml";
| > xmlns:tal="http://xml.zope.org/namespaces/tal";
| > xm
Velko Ivanov wrote:
Dmitry Vasiliev wrote:
Maybe we need always check security map at the root folder?
I don't believe this is the solution. Altrough it will solve my example,
it wouldn't help in other scenarios.
I would eventually make ZopeConnection and ZopeCursor locatable, if they
aren
Martijn Faassen wrote:
Gary Poster wrote:
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be
missing in zc.catalog. Am I at all on the right track wit
Julien Anguenot wrote:
> Ok the problem is the doctype declaration on top of the macro files that
> force the tal interpretor to enter html mode and as far as I understand
> you can't have mix moded macros.
Exactly. I forgot to mention that in my follow-up...
Btw, doctype declaration is something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp von Weitershausen wrote:
> Julien Anguenot wrote:
>
>>I got a problem with the standard macros use and the XML header.
>>
>>I've a view defined like the one below :
>>
>>
>>>xmlns:tal="http://xml.zope.org/namespaces/tal";
>>xmlns:metal
Julien Anguenot wrote:
> I got a problem with the standard macros use and the XML header.
>
> I've a view defined like the one below :
>
>
> xmlns:tal="http://xml.zope.org/namespaces/tal";
> xmlns:metal="http://xml.zope.org/namespaces/metal";
>
>
>
>
>
>
> And there, I got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok the problem is the doctype declaration on top of the macro files that
force the tal interpretor to enter html mode and as far as I understand
you can't have mix moded macros.
If you change the doctype declaration with the xml header and add the
xml
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I got a problem with the standard macros use and the XML header.
I've a view defined like the one below :
http://xml.zope.org/namespaces/tal";
xmlns:metal="http://xml.zope.org/namespaces/metal";
>
And there, I got the
On Tuesday 30 August 2005 11:55, Adam Groszer wrote:
> Is there any way to fool the Z3 XML-RPC publisher to unmarshall
> strings *always* as unicode? I think the problem is that xmlrpclib
> tries to convert all strings to str, but in Z3, all strings should be
> stored as unicode. Even better that z
On Tuesday 30 August 2005 11:55, Adam Groszer wrote:
> Is there any way to fool the Z3 XML-RPC publisher to unmarshall
> strings *always* as unicode? I think the problem is that xmlrpclib
> tries to convert all strings to str, but in Z3, all strings should be
> stored as unicode. Even better that z
On Wednesday 31 August 2005 05:41, Martijn Faassen wrote:
> Okay, this is clear. It's not that clear to me how to efficiently make a
> subscriber only handle one object type (I've been using the "is this a
> IFoo? If not, return" pattern at the start of subscribers), but that's
> another discussion
Gary Poster wrote:
On Aug 30, 2005, at 1:57 PM, Martijn Faassen wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be
missing in zc.catalog. Am I at all on the right track with my
thinking on it?
I
Jim Fulton wrote:
[snip]
It would be helpful if someone could explain the motivations behind
the extent catalog, by the way -- this information seems to be missing
in zc.catalog. Am I at all on the right track with my thinking on it?
What information?
Sorry for being unclear. I meant the inf
Janko Hauser wrote:
>
> Am 31.08.2005 um 10:25 schrieb Jean-Marc Orliaguet:
>
>> Hi !
>>
>> I have been thinking about Jim's question: "why do you need
>> relations?".
>> Some obvious answers came first others emerged later on, now I think
>> that most of them are emerged, so I'll try to summariz
34 matches
Mail list logo
