On Wed, Apr 29, 2009 at 6:52 PM, Drew Baird (Volt)
<[email protected]> wrote:
> Mostly Questions:
> Do you have the latest dotnet code? (Have to ask - I assume yes.)
Yes.
> I am concerned we had to modify program.cs. We should only have to change the
> config file so that is an issue. When you say: "Since PHP doesn't make any
> assumptions about the end point, doing this is frowned upon in a loosely
> coupled application." Do you mean we need to generalize the dotnet service
> to not make assumptions about the end point?
When PHP talks to an end point all it knows is that it's talking to a
secure end point. App.config in business service I see the following,
<client>
<endpoint address="http://localhost:8000/tradeorderprocessor";
binding="basicHttpBinding"
bindingConfiguration="Client_BasicHttpBinding"
contract="Trade.OrderProcessorContract.IOrderProcessor"
name="Client_BasicHttpBinding" />
<endpoint
address="http://localhost:8000/tradeorderprocessor/msec";
binding="wsHttpBinding"
bindingConfiguration="Client_WsHttpBinding_M_Security_OPS"
contract="Trade.OrderProcessorContract.IOrderProcessor"
behaviorConfiguration="OPS_ClientCertificateBehavior"
name="Client_WsHttpBinding_M_Security_OPS">
<identity>
<certificate encodedValue="..." />
</identity>
</endpoint>
<endpoint address="http://insert_address_here";
binding="customBinding"
bindingConfiguration="Client_customBinding_M_Security_OPS_WS02"
contract="Trade.OrderProcessorContract.IOrderProcessor"
behaviorConfiguration="OPS_ClientCertificateBehavior"
name="Client_customBinding_M_Security_OPS_WS02">
<identity>
<certificate encodedValue="..." />
</identity>
</endpoint>
</client>
I deliberately omitted the encodedValue in certificate elements for
brevity. Please correct me if I'm wrong, I interpreted the above as
different end points having different binding policies. So, if there's
a Metro OPS you need another entry here right? That's the concern I'm
having Drew.
Bye,
-Chintana
--
http://engwar.com/
