Will iControl support SOAP 1.2 and document/literal??

We are currently investigating suport for SOAP v1.2 in iControl. From an implementation standpoint there really isn't much that's changed but there are several items that cause backward compatilbility problems. We currently support several toolkits that are still not up to v1.2 in their client side support so we are holding off until all the toolkits come up to speed.

 

 

Are there any specific features of 1.2 that you need that are not compatible with our 1.1 implementation. Input could help us prioritize these features in upcoming releases.

 

 

As for doc/literal, that's a tough one as the SOAP stack we are using (home grown) doesn't support doc/literal and it's quite a bit of work to retool the serializers to support it. Currently the only thing holding us back from WS-I compliance is our support for doc/literal so it is on our radar but honestly you are the first customer/user to request it. Again, is there a specific requirement for doc/literal that you have?

 

 

-Joe

My question about SOAP 1.2 was borne only out of curiosity, no requirement.

 

 

As for the doc/literal SOAP messaging style, I am thinking of using the new web-services communication infrastructure from Microsoft called "Indigo" (check out below link) to send the SOAP messages to iControl. Indigo *might* only support doc/literal.

 

Thanks,

 

Karthic.

 

 

http://msdn.microsoft.com/longhorn/understanding/pillars/indigo/default.aspx

I've been involved with Indigo since it's early inception in WSE as F5 has been included in the early design reviews. I know that MS strongly supports doc/literal but I'd be surprised if they don't support rpc/encoded as a fallback. If the Indigo team decides not to support rpc/encoded you can be sure we will apply the efforts to work with them.

 

 

-Joe