On Sun, Oct 04, 2009 at 04:33:28PM -0400, Vio wrote:
> You're right. Keeping a running Gimp daemon in memory would most
> certainly speed things up (for subsequent calls)
This worked very well with gimp-perl and mod_perl 10 years ago.
It was relatively easy to establish a persistent connection from
mod_perl to the gimp-perl server. Just as in database connections,
each Apache child maintained a socket connection to gimp-perl.
It's just a matter of sorting out the socket permissions, as you have
learned. For security purposes, I ran gimp as a different user, but
granted permissions on the socket to www-data, and allowed gimp to
write to a specific directory in the document root to enable caching
of output images.
The performance was amazing, even 10 years ago.
I'm not sure if gimp-python has a similar server mode, but if it does,
I'm sure that mod_python could cache the connections for similar
performance levels.
Cheers,
Tom
--
-- Tom Rathborne --------------------------------------------------------------
The most perfidious way of harming a cause consists of
defending it deliberately with faulty arguments.
-- Friedrich Nietzsche
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
