As I mentioned previously, I'll be at MIX this year on a panel discussing ASP and PHP interoperability, along with Jesse Liberty, Bill Staples, Joe Stagner and Brian Goldfarb.
I've been told that MIX has sold out and that there is a lot of interest in our slot, so I'm sure we'll have plenty to talk about, but I'm looking for questions to break the ice and get things rolling.
If you have any questions, comments or other insights on PHP running on Windows, or on getting PHP apps working together with ASP.net apps, please comment on this blog post, and I'll try to work them into the panel, and to feed back the results of the discussion here on my blog.
If for some reason your comment doesn't go through, or if you prefer email, you can also mail them to me at wez@php.net.
Maybe i'm off topic here, but since there is no much traffic here lets try:
We on http://www.icomsw.com/ have some crm and erp applications.
When we was looking for reasonable model that will allow our applications run out of the office, mean on windows mobile hardware (aka pocket or smartphones), we just found that the traditional web programming that assuming the customer is online, can't do the job in most of cases (most of places and customers - here in israel and worldwide)
The chosen model was using local web server on each PDA that will synchronize itself against the application while online. Now all we have was to choose the web server and scripting language ....
Web server: The native choose was IIS for WINCE.
Scripting: ASP.NET is not working on WINCE5.0 PHP - there is http://mobileleap.net/hph/ but we can't trust on quite unmaintained, close code produced by unknown small company who shift only half year demo. ASP - look like default no?
But we quickly learnt that: 1. The documentation and the accumulated experience with IIS on WINCE is poor! 2. The hardware vendor (HP and so on) are the absolute authority that can make any PDA containing the ASP\IIS into his hardware 3. There is no real world thing you can realy run on naked ASP- e.g, sqlite who have quite stable port for WINCE and we want it as the local database.
What we did? We just port our WINCE PHP port (you can call it PHPCE if you like) with the CGI sapi. That took us more then 8 programing mounths due to our lake of familiarity with both PHP internals and WINCE internals but after all, the delay was realy worthwhile since our simple php developers, our windows base php development and testing environment and the developers and most of the code itself was saved and we discovered huge new market ....

