Just to clarify: plenty of Intraweb, experience, just not with regards to the Linux side of Intraweb life. I've had no issues with php or mysql on windows either, much as I might prefer them in a Linux flavor, not all of my clients do and so we've adapted to those as needed.
Breaking just the intraweb piece out to it's own server might also be an option for you to consider, leaving the php and mysql in place and changing the connecting pieces that tie in Intraweb from a windows server.
Main Topics
Browse All Topics





by: irishbuddhaPosted on 2009-09-29 at 07:48:06ID: 25449625
While I don't have a lot of direct experience in the exact issue, I've read plenty on intraweb and hit my own deployment and configuration issues that have sent me reading up on a lot of the same topis...here's some information that should help you get started:
iki/Lazaru s_%28softw are%29). Cross Platform Delphi-esque IDE.
iki/Zeus_W eb_Server) , though being a hosted environment this may not be available.
If that will work though, this might be the best option for you in continuing with Intraweb. You lose Linux, but, the rest of your tools are still there with minimal differences and you can forge ahead without being trapped in a corner.
Kylix is dead. No argument there. From what I've read via the newsgroups and several blogs though, one option is probably Lazarus (http://en.wikipedia.org/w
Standalone and Service deployment for win32 are non-starters as you note, but several Intraweb posters in the newsgroups and various blogs have noted success with WINE, no clue on the details of the deployment or configuration, but, it might be a possible solution for you. This may be a non-starter with your host though...
As far as ISAPI goes, it is a function of IIS as you noted. Fortunately, IIS is not the only ISAPI functionality player in town. A quick search shows for Apache ISAPI brings up the Apache Module mod_isapi, though it looks windows only on a quick scan. You might check out Zeus (http://en.wikipedia.org/w
As for losing PHP/MYSQL, both are now compatible with windows, and if you have to lose Apache, you are now back to haveing #2 and #3 as options (#1 personally is more testing oriented than anything, but that's me). There are some small differences in the php side depending on your code and delimiters, possibly some functionality, but the majority of the libraries should be dead on (http://windows.php.net/).
Again, parts of this are purely reading knowledge, but hopefully this will get you pointed in the right direction.