Hmm, I don't know where you have this information from and I won't comment it with any other words than that it's simply nonsens!Please do not skip the 'old' TV engine. I've tried the TVserver3 many times now. I'm sticking with the old TVengine. I think it will take at least a year (maybe even two) before the new engine will be a standard component in MP. There is not yet a way to include all components needed in one installer (this is not possible for SQLexpress). It's been discussed and there seems to be no real interest to make it easier to implement the TVengine. Untill that happens the TVserver/client 3 will not be a standard. If you ask me, it could well be that MP is going to stick with the 'old' TVengine and upgrade it. The TVengine 3 could be optional forever.
Supporting the old AND the new TV Engine will lead us to 2 completely different webinterfaces in the backend. I definately won't do anything for the old TV engine. The old webinterface is still downloadable and should work at least in basic functions. And hey, we'll need some time too, until we have a finished/useable webinterface for the new engine. Until then the situation might be completely different...
What do you mean with that? Of course any php script can (IIRC if you installed the soap extensions) consume webservice functions from any given webservice. That's what the concept is about: to have a language-independent communication.Is it possible to make the webservice support php?