[openamq-dev] Using the static OpenAMQ libraries in a sharedlibrary seems impossible, except on i386 platforms...

[Jacobus Geluk]

Exactly, that is precisely what I am trying to do, the problem only is when
and how often to launch such a single-threaded-amqp-client from the apache
module. Per apache-child-process, per-connection, or per request. I think if
the amqp client could start up fast enough a per-connection approach would
be best since you can assume that every request comes from one user
sequentially. If it does not start up fast enough I could pre-launch a
certain number of amqp-clients. If the memory foot-print per client would
also be friendly, it could even scale up :-).
This is probably off topic though...

On Sat, May 31, 2008 at 11:15 AM, Pieter Hintjens <ph at imatix.com> wrote:

> On Sat, May 31, 2008 at 9:28 AM, Jacobus Geluk <jacobus.geluk at gmail.com>
> wrote:
>
> > I keep digging, but I am also trying to create a workaround, since I
> expect
> > more problems anyway, since both Apache and OpenAMQ are based on their
> own
> > versions of APR. The workaround would be to have the apache module
> > "mod_amqp" talk via shared memory and/or socket and/or pipe with a
> companion
> > daemon that does the actual work (and can be build in C++).
>
> It strikes me that a simple single-threaded AMQP client in C/C++ would
> be the simplest answer.
>
> -Pieter
> _______________________________________________
> openamq-dev mailing list
> openamq-dev at lists.openamq.org
> http://lists.openamq.org/mailman/listinfo/openamq-dev
>



-- 
Met vriendelijke groet,
Jacobus Geluk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openamq.org/pipermail/openamq-dev/attachments/20080531/f0967feb/attachment.htm