bob smith wrote:
I had the same error with OSX 10.3 and Apache 2.2.0. The fix was to add
the fourth parameter required by deleting lines 214 & 216:
if ((rv = apr_socket_create(&aprsock, AF_INET, SOCK_STREAM,
#if (APR_MAJOR_VERSION > 0)
APR_PROTO_TCP,
#endif
I'd like to know why
Hi,
I had the same error with OSX 10.3 and Apache 2.2.0. The fix was to add the
fourth parameter required by deleting lines 214 & 216:
if ((rv = apr_socket_create(&aprsock, AF_INET, SOCK_STREAM,
#if (APR_MAJOR_VERSION > 0)
APR_PROTO_TCP,
#endif
r->pool)) != APR_SUCCESS
I am still not convinced that polling is a good solution for long queries.
One good reason for this is that you can't implement real time
application anymore: a chat board, real time stock quotes, etc...
Isn't it better to store the tcp socket file handles left open in a
connection pool?
As so
I have also updated the wiki with similar changes (splitting the
javascript, allowing polling to be disabled and stopped once it is
going). It's probably slightly different than your changes in svn, so we
should probably figure out which is better suited to the necessary tasks
and go with that
I have now incorporated your ajax_clientPollingInterval() to AjaxPage as
well and separated the responseTimeout parameter from the clientPolling
flag. Adding some more docstrings and splitting the Javascript in two
parts now makes the whole thing much better understandable.
-- Christoph
Sorry, I should have waited for your response before doing it on my
own. That looks good. However, I really would like to be able to
switch off the polling completely. This spares loading and running the
Javascript for the polling mechanism, and the shutdown, with all
possible Javascript erro
John Dickinson wrote:
Instead of turning the polling off, would setting the client polling
interval to some big number be good enough? I added an
ajax_clientPollingInterval to AjaxPage so that a child page can easily
set the polling interval (long if it doesn't need it, short if it does).
Sor
sophana wrote:
I agree with you that webware is not designed for doing this kind of stuff.
If you want to do long running queries, I suggest that you bypass apache
and webware, and implement a separate dedicated (python) server that
supports these very long running queries, without the timeout
However, I'm actually wondering whether you really always need to run
this background polling. If requests are always answered within the
timeout interval (which is set to 100 seconds), that mechanism should
be never needed. For instance, in the "AjaxSuggest" example, it will
be surely not ne
However, I'm actually wondering whether you really always need to run
this background polling. If requests are always answered within the
timeout interval (which is set to 100 seconds), that mechanism should
be never needed. For instance, in the "AjaxSuggest" example, it will
be surely not ne
John Dickinson wrote:
I've got a new implementation that solves both of these problems, but I
can't seen to get in to the wiki to post it.
Thanks a lot. I have already checked it in to the SVN repository.
BTW, I have restarted the Wiki and let it use the current Webware 0.9.
Should be better
11 matches
Mail list logo
