Since version 4.0, what are the most confusing parts of WCF? -
Since version 4.0, what are the most confusing parts of WCF? -
this question inspired jon skeet's question here asked people pain points linq hope question isn't out of place ...
version 4 of wcf tackled, probably, 1 of areas many people struggled wcf - namely configuration. however, tagged set of questions , other forums there other areas people struggle with.
i've made bunch of blog posts , screencasts in past trying focus on mutual issues (such duplex, sessions, etc). i'm planning set want focus on things causing people problems changes in version 4.0.
areas see things like
instancing , threading security rest support wcf , silverlight large message processing / streaming configuration (still) serializationand i'm sure there more, i'd input , maybe can create sure product team feedback greatest pain points people have wcf
i participate both here , on msdn , after answering many questions sentiment greatest pains people have are:
configurationconfiguration pain more before. simplified configuration makes lot of things worse because before simplification if made error in configuration got exception. today create typo in service name (or forgot add together namespace) , service silently utilize configuration.
securitysecurity paint, pain , pain.
security complicated , wcf making more blured because programmers on other platforms utilize shared vocabulary based on real ws standards, wcf uses own names. only subset of security standards implemented - 1 failure missing username token profile digested password straight in wcf. when hosting services in iis security features in services shared iis , restricts settings whole site / virtual directory. when hosting services in iis basic authentication handled in iis - must build custom module handle differently (but if utilize self hosting can utilize custom user name password validator in wcf straight - iis should back upwards well). bad back upwards generating security configuration when creating proxy wsdl. best wcf has custom binding. custom binding on client side useful when service wcf , uses custom binding. need improve back upwards in security binding element provide same configuration features counterpart in code. wsdl importer should able utilize new binding element , create proxies secured services. 1 time such importer not able import wsdl sure default wcf doesn't back upwards security requirements expected service. reststill lot of people don't see difference between rest , soap , mutual error adding service reference rest service. problem of rest added unified protocol independent api rest heavy protocol dependent , not message oriented. improved in web-api.
protocolsit looks new protocols or protocols versions not added wcf.
extensibilitywcf has great extensibility unless trying extend existing feature. if decide extend existing implementation can't. illustration add together mentioned username token profile digested password must scratch. cannot extend existing user name implementation.
edit: lastly 2 personal pains.
wcf
Comments
Post a Comment