IMHO, if you are going to be creating a GUI, then use a PR that is
specifically designed to give good X-platform GUI's. APR is not that
project. If you had a non-GUI project, then APR would be a much better
fit for you.
Ryan
On Tue, 27 Aug 2002, TC wrote:
> >> Beyond the portability are there
>> Beyond the portability are there other benefits you have noticed
>> using APR in the last few years on the Apache Web server
>
>I would be happy to answer this. But first, let me comment on a few of
>the options above, and some of what we have learned. I want to be clear
>that I am not bad-mou
At 10:45 AM 8/27/2002, Ryan Bloom wrote:
On Mon, 26 Aug 2002, TC wrote:
... The hardest thing to grasp is the memory pooloing.
> -how about performance??
Apache has not suffered from performance problems related to APR, although
any portable run-time does incur some performance penalty. We have a
On Mon, 26 Aug 2002, TC wrote:
> Hi
> Over on the asterisk mailing list ([EMAIL PROTECTED]) there is a little
> discussion on what would be the best match for a portability layer
> for the core phone functions in asterisk...
>
> custom brew
> cygwin
> GTK
> ACS
> Netscape etc etc
>
> Beyond the
Hi
I posted this before I go registered for this List I am not sure
if it got seen, sorry if a report ..
Over on the asterisk mailing list ([EMAIL PROTECTED]) there is a little
discussion on what would be the best match for a portability layer
for the core phone functions in asterisk...
custom b
Hi
Over on the asterisk mailing list ([EMAIL PROTECTED]) there is a
little
discussion on what would be
the best match for a portability layer
for the core phone functions in asterisk...
custom brew
cygwin
GTK
ACS
Netscape etc
etc
Beyond the portability are there other benefits
you have
