Why WCF custom (In process or isolated) adapter is better than
the other WCF adapters. When I discussed with a BizTalk team working
for leading apparel client, they have used the custom adapter
extensively and they haven’t used any other WCF adapters. I got some
answer like
“For example one of the requirements is to fetch a column from a
table which is not a value but a XML message instead. In this case using
WCF-custom developer can type poll to have better control on the table
column that are fetched.”
Yes the above statement is true. But it has more reason, after some exploration and I found the following list of usage
- Implement and exploit extensibility points.
- Have full access to properties exposed by bindings/behaviors.
- Enable the use of the bamInterceptor endpoint behavior.
- Export/Import the binding configuration.
- Disable a receive location on failure.
- Run an http-based Receivel Location within an in-process host.
- Use bindings (e.g. wsDualHttpBinding) for which a WCF Adapter does not exist.
Not sure, Why we need other WCF adapters like WCF-NetTcp,
WCF-NetMSMQ etc. Since WCF-Custom Adapter (Inprocess & Isolated) can
do the job?
Only one use, I can think of , we can quickly configure other WCF
adapters than the custom adapters and we don’t require to worry about
any other behavior of the service. please comment if you know more
reasons
No comments:
Post a Comment