How can I avoid huge communication classes in WCF?
        Posted  
        
            by mafutrct
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by mafutrct
        
        
        
        Published on 2010-03-15T10:16:23Z
        Indexed on 
            2010/03/15
            10:19 UTC
        
        
        Read the original article
        Hit count: 186
        
wcf
My understanding is that all contract-implementing code has to be in a single class, that can become very large, obviously. How do I avoid this? I really prefer to have a few small classes doing one part of the communication with clients than a single behemoth class.
The only idea I could think of is using multiple interfaces implemented by a single class split up by partial, but I don't this this is really solving the issue.
© Stack Overflow or respective owner