don't want to include message call and response envelopes in service interfaces

Yanıt don't want to include message call and response envelopes in service interfaces

  • 17 Temmuz 2012 Salı 14:55
     
     

    There is extra information I need to add to a client's communication with a WCF service.

    The prevailing strategy seems to be to include caller and response envelopes in the service interface. This doesn't feel like the best way to me, since it's a generic concern of service communication. I would prefer not to tangle that into every interface, but rather 'sideband' that information.

    Is this possible? If so, are there any good code examples?

    Also - any problems with this approach, reasons I might not want to do it this way?

    Paul



    • Düzenleyen PJ7 17 Temmuz 2012 Salı 14:55
    • Düzenleyen PJ7 17 Temmuz 2012 Salı 14:56
    •  

Tüm Yanıtlar

  • 18 Temmuz 2012 Çarşamba 02:16
     
     Yanıt

    I am not sure about your requirement.... But sounds like you want to send some generic data to each operation call and you dont want to tie that in your interface definition ....

    In that case  you can utilize the Message Inspector


    Tanvir Huda Application Architect/Consultant http://thetechnocrate.wordpress.com/