On 24 Jan 2007 at 11:39, Also Sprach Matt Sergeant:
On 24-Jan-07, at 10:52 AM, [EMAIL PROTECTED] wrote:
Given the above (I presume it's correct) the ways around it are
1) Have a separate DBI daemon that processes requests and
uses Danga.
In the next release I hope to build a job
On Thursday, 25. January 2007 11:10, [EMAIL PROTECTED] wrote:
On 24 Jan 2007 at 11:39, Also Sprach Matt Sergeant:
On 24-Jan-07, at 10:52 AM, [EMAIL PROTECTED] wrote:
Given the above (I presume it's correct) the ways around it are
1) Have a separate DBI daemon that processes requests
On 25-Jan-07, at 5:10 AM, [EMAIL PROTECTED] wrote:
Not sure how feasible it is, but we'll give it a go.
Will it be another ax2 server that essentially does RPC
from the main server? Something along the lines of using Danga
to listen on a FD (as per the Ax2 docs)?
The methods on the main ax2
On Wed, Jan 24, 2007 at 03:51:45PM +0100, J?rg Walter wrote:
On Wednesday, 24. January 2007 13:29, [EMAIL PROTECTED] wrote:
I was wondering if it would be possible to contribute to the project a
mysql db app? They don't come more dynamic than a db app :)
Did you solve the problem of
On Wednesday, 24. January 2007 13:29, [EMAIL PROTECTED] wrote:
I was wondering if it would be possible to contribute to the project a
mysql db app? They don't come more dynamic than a db app :)
Did you solve the problem of asynchronous queries? I think that was the main
problem last time. You
On 24 Jan 2007 at 15:51, Also Sprach Jörg Walter:
On Wednesday, 24. January 2007 13:29, [EMAIL PROTECTED] wrote:
I was wondering if it would be possible to contribute to the project a
mysql db app? They don't come more dynamic than a db app :)
Did you solve the problem of asynchronous
On 24-Jan-07, at 10:52 AM, [EMAIL PROTECTED] wrote:
Given the above (I presume it's correct) the ways around it are
1) Have a separate DBI daemon that processes requests and
uses Danga. ie A db request is palmed off to the DBI server
and the DBI server gives Ax2 a kick when the data has been
