Richard Turner - What is your advice to developers who are thinking about Indigo and interoperabilit

Play Richard Turner - What is your advice to developers who are thinking about Indigo and interoperabilit

The Discussion

  • User profile image

    I work for a software company that writes software for the hospitality industry.  We are re-writing and expanding our support for peripheral devices, pagers, PDAs, cell phones with new .NET apps and services.  For interoperability, we chose to use remoting over web services, primarily because of the technical challenges to our customers in setting up, securing, and maintaining IIS.  Now, after listening to Richard Turner's discourse on Interoperability and Indigo, I fear we may be taking a dead-end path.

    So I am looking for someone who may be able to provide answers to the following questions:

    - Will Indigo Services require configuration of IIS?

    - It may be necessary for us to support Windows 2000 and XP for many years with our current customers.  Can Indigo Services be hosted on these OSs?  Will applications running on these OSs be able to act as clients to Indigo Services?

    - We expose some of our remoting assemblies via HTTP and host at least one in IIS.  Will Indigo Services offer interoperability with these configuations?  Will we be able to write an Indigo wrapper around a remoting DLL?

  • User profile image
    Thought I'd replied to this forever ago! Sorry it didn't seem to make it to the site! Sad

    In answer to your questions:

    Q1: "Will Indigo Services require configuration of IIS?"
    A1: Yes ... if you want to host your Indigo services in IIS. No ... if you don't! You can host Indigo services in any CLR application - regardless of which transports, encodings etc. that your services require.

    Q2: (Paraphrased) "What platforms will Indigo support?"
    A2: Windows XP (SP2+), Windows Server 2003 (SP1+) and Windows Vista.

    Q3: (Paraphrased) "Will Indigo interop with Remoting endpoints?"
    A3: No. Remoting is not compatible with Indigo on the wire. There are several technical reasons for this including the fact that Remoting uses RPC-encoded SOAP whereas Indigo, ASMX and pretty much everything else that talks SOAP these days uses document-literal-encoding. Also, if you're using Remoting with the SOAP/HTTP channel, you should read my paper on ASMX/ES/Remoting perf - you might be compromizing your systems performance! Wink

    Hope this helps.

    Rich Turner

Add Your 2 Cents