Hi there,
I'm working on removing BBB warnings of our current app for 3.3.
For the directive it was possible to give the factory some
parameters like this:
Now, with the directive that's not possible.
--
Best regards,
Adam mailto:[EMAIL PROTECTED]
--
Quote of the d
On Mon, 15 May 2006 21:19:02 +0200, Paul Everitt wrote:
> Mozilla has some support for keeping the server connection open and
> pushing messages to the client:
>
>http://www.xulplanet.com/tutorials/mozsdk/serverpush.php
>
> Two asides:
>
> 1) Is this better for zope3-users?
That's good news
On Mon, 15 May 2006 19:02:15 +0100, Martin Aspeli wrote:
> I'm pretty sure the fundamental AJAX pattern is that you send
> XMLHttpRequests on some event, either a timer (so it polls) or a user
> action (e.g. an on-click handler). I've never seen the pattern of a
> persistent connection ... if you h
Jeff Rush wrote:
Benji York wrote:
Zachery Bir wrote:
I think Benji's commenting on the fact that you're creating a
synchronous connection when you hold it open like that.
Exactly. As Jean-Marc noted, Jeff's talking more about "streaming"
than "asynchronicity" (is that a word?).
Well th
Jeff Rush wrote:
>
>Provide a chat window at the bottom of a page, in which a student
>interacts
>with a teaching app and members of his team. In the upper portion of the
>page, the teaching app alternately presents proficency questionaires and
>lessons.
This seems to be very similar to our "li
On 5/15/06, Jeff Rush <[EMAIL PROTECTED]> wrote:
Now that's odd, because to me having 1,000 clients repeatedly poll the server
every second, and potentially tearing down/making new TCP connections is less
scalable than on a modern OS keeping around 1,000 threads or twisted
Well, if you're certa
Tarek Ziadé wrote:
Jeff Rush wrote:
what does your code actually do ?
Provide a chat window at the bottom of a page, in which a student interacts
with a teaching app and members of his team. In the upper portion of the
page, the teaching app alternately presents proficency questionaires and
Fred Drake wrote:
On 5/15/06, Jeff Rush <[EMAIL PROTECTED]> wrote:
I got the definition from Wikipedia:
http://en.wikipedia.org/wiki/AJAX
Yes; we agree on this definition of AJAX, I think. :-)
Sorry, I was addressing what I erroneously thought was confusion over what the
'A' meant.
Hi Roger, hi Jeff,
Roger wrote:
>
>See this for more information, but don't ask me if it's working.
>
>http://svn.zope.org/zope3org/trunk/src/zorg/live/README.txt?rev=66712&view=markup
>
It works at least for our purposes. We are using an experimental LivePage
application here at our institute. "E
do you mean HTTP streaming? http://ajaxpatterns.org/HTTP_Streaming
After reading that excellent article, yes, that is what I mean. I want to use
Donovan Preston's LivePage technology, which is described in a link from tha
article, under Zope3.
I recently noticed something that makes it tr
Hi all,
There is such a thing in z3!
Or at least in the "new" zope3.org implemnetation ;-)
I remember that Uwe Oestermeier was developing something
like a livepage which can receive and send streams of HTML
on a open request.
See this for more information, but don't ask me if it's working.
htt
On Mon, 15 May 2006 18:49:24 +0100, Jeff Rush <[EMAIL PROTECTED]> wrote:
I looked at MochiKit and studied the Async package, but perhaps I didn't
understand it. I only saw ways for the client to sneak HTTP REQUESTSs
to the server behind the user's back, but nothing for the server to
reach
On May 15, 2006, at 1:49 PM, Jeff Rush wrote:
Benji York wrote:
Zachery Bir wrote:
I think Benji's commenting on the fact that you're creating a
synchronous connection when you hold it open like that.
Exactly. As Jean-Marc noted, Jeff's talking more about
"streaming" than "asynchronicity"
Benji York wrote:
Zachery Bir wrote:
I think Benji's commenting on the fact that you're creating a
synchronous connection when you hold it open like that.
Exactly. As Jean-Marc noted, Jeff's talking more about "streaming" than
"asynchronicity" (is that a word?).
Well the connection itsel
On 5/15/06, Jeff Rush <[EMAIL PROTECTED]> wrote:
I got the definition from Wikipedia:
http://en.wikipedia.org/wiki/AJAX
"Ajax, shorthand for Asynchronous JavaScript+CSS+DOM+XMLHttpRequest, is a Web
development technique for creating interactive web applications."
From the page of the guy tha
Jeff Rush wrote:
> Benji York wrote:
>> Jeff Rush wrote:
>>
>>> Just checking if I'm missing something -- with the removal of HTTP
>>> streaming/chunking in 3.2, this means that the async bi-directional
>>> persistent socket communications associated with Ajax is NOT
>>> possible at this time?
>>
>
Zachery Bir wrote:
I think Benji's commenting on the fact that you're creating a
synchronous connection when you hold it open like that.
Exactly. As Jean-Marc noted, Jeff's talking more about "streaming" than
"asynchronicity" (is that a word?).
FWIW, I've been using MochiKit's Async packag
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional
persistent socket communications associated with Ajax is NOT possible
at this time? That a request/response must quickly run to completion
on
On May 15, 2006, at 1:23 PM, Jeff Rush wrote:
Benji York wrote:
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of
HTTP streaming/chunking in 3.2, this means that the async bi-
directional persistent socket communications associated with Ajax
is NOT possible at
Benji York wrote:
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional
persistent socket communications associated with Ajax is NOT possible
at this time?
Don't know if it is or isn't, but tha
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional persistent
socket communications associated with Ajax is NOT possible at this time?
Don't know if it is or isn't, but that's a novel definitio
Jeff Rush wrote:
> Just checking if I'm missing something -- with the removal of HTTP
> streaming/chunking in 3.2, this means that the async bi-directional
> persistent socket communications associated with Ajax is NOT possible
> at this time? That a request/response must quickly run to completio
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional persistent
socket communications associated with Ajax is NOT possible at this time? That
a request/response must quickly run to completion on a thread and canno
Hi there,
Is anyone planning a Zope 3 sprint at EuroPython? And if so, in the days
before or the days after EP?
Regards,
Martijn
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archi
24 matches
Mail list logo