Every hour? how about using a cronjob?

I don't think there's a kinda timing issue. Your browser would throw an error if it couldn't establish a connection to your webserver. It seems more like your webserver just terminates the connection without sending a response at all.

You can detect a BOM when opening a UTF8-encoded file in an editor that's not capable of UTF-8 files or with a HEX Editor. If there's a BOM in your file, you'll see two weird looking charaters. The other typical reason for your issues are whitespace in included scripts before/after PHP tags.

no, rather a POST request, unless your configured xajax to use GET instead

Try enabling error reporting and let us know what happens:

Thanks Ed,

I know, the requirements for the screen resolution are quite high at the moment. Perhaps I'll go down for a 1024x768 minimum resolution, but the size of the map would suffer a lot. We'll see

Hi Artur,

Oliver just pointed me to this topic. I'm really sorry for the lack of presence. We have an almost finished 0.6 release in the trunk for a while now, but unfortunately the financial crisis didn't affect my company and everything is running a bit too well here. I'm swamped As Oliver already said, CtC is also pretty busy and so we kinda messed things  up a bit here. (If someone is selling time, let me know!)

This year is almost over and the holidays are very close. I can't promise anything for the end of this year, but I'm sure we'll be able to put everything together in January.

The current version in trunk is PHP 5 strict, supports JSON as well as the old XML responses and contains some other minor improvements. CtC was going to add some more htmlControls but since that idea is becoming a bit too big we'll leave it out for 0.6 and might maintain it separately later. Oliver, feel free to add anything I forgot here Have to read the trunk again to remember all changes we made so far.

Hi Sebas,

thanks for pointing that out. I'll have a look at it asap

Please do not modify any core files. You can define XAJAX_DEFAULT_CHARACTER_ENCODING on your own before including xajax. Xajax detects the encoding and sets decodeUTF8input automatically. You also have to make sure that all scripts / files / databases use the same encoding.

As long as xajax works it's not a problem related to xajax. I'm not familar with php hosting on Win but you can try to use the AIO version (look into the download section). One user reported that the includes in his dev enviroment on win were very slow and the AIO version solved it for him.

The image files are compressed and when you open an image file to modify it it's converted into raw data. There's no formula to calculate the raw image size - JPGs for instance vary per compression level.