The application can reside either way. One setup on one server or one setup to many domains. For example a broker may want to share the feed with his agents. Permissions are set individually by agent for part or all of the IDX to be displayed. We have done the same thing with open realty where we have one parent site and 20+ child sites. The child sites pull the data from the parent server. We originally built this for a developer who wanted to incorporate IDX into his client's sites without the hassle of installing OR on them

The scripts are OOP php classes. A brief explantation: With OOP each object is independent and objects can be swapped in and out without effecting other objects other than enhancing the entire application. An environmental incompatibility would be easy to work around.

We have not tested it on with php 5 but plan to do so and if it needs tweaking to work we will take care of it. No html or commands are embedded in them that would lock it in to a particular environment. Mike (programmer) was using an IDX script we did for Monroe county Florida as the base and he must have hard coded the county in it. (all IDXs are custom) We were concerned about the scaling. Previously we only had 20000 listings to test it on. Thank you. One of our client developers is testing a simplified backend with 20 sites. Once we finalize the format I will put up some screen shots and perhaps setup a demo.