Mart: what's your current status of running the server on Windows?
I remember seeing somewhere a sub you replaced to make it work.
I want to change things so it works fine out-of-the-box on Windows or Unix.
I'm starting to setup things here on my Windows machine, just for pain.
The protocol will now return galleries and relations. See notes/protocol.
We'll be supporting XML-RPC also, but it's always nice to have lots of different interfaces available, as it makes work easier on client authors. Evan wanted this interface.
I can't help but notice that the Windows FotoBilder client makes a new connection for each request it makes. Doesn't HTTP support some sort of sustained connection? What is that called? (I recall a header of the sort "Connection: ...") How is this related to keepalives?
I've looked around in the docs and on the web, but the best I can find is a flag, INTERNET_OPTION_KEEP_CONNECTION, which is documented as unimplemented in most sources I can find and doesn't do much on my system (Win2k, IE6).
I never did get around to playing with FotoBilder server on Windows, but I did include Mart's work-around in the source.
If you're on Windows, put:
$FB::WINHACK_GPICAPPEND = 1;
in your etc/fbconfig.pl and let me know if it works. Looks like you'll need to make an $FB::HOME/tmp directory first that's writable by the webserver.
Mart --- what does POSIX::tmpname return on Windows? Isn't it a full path? How can you just append that to $FB::HOME/tmp without making a bunch of directories first? Can't you just do what jredburn suggested and prefix the single argument version of Write to use "jpeg:" or "gif:" to whatever POSIX::tmpname returns?
In any case, the code still works on Unix.
Unless I hear support for $WINHACK_GPICAPPEND it'll be removed. If it does work, though, then we should document it somewhere. (Somebody want to write a quick guide to running the server on Windows?)
[17:57] brad: what's with you and kittens, anyway? :)
[17:57] evan: i like them
[17:57] evan: they are cute and sweet. :)