Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
I'm building a WCF service project. It has a few layers, like Data, Business or Hosts. I usually also added "Clients" folder and "Proxy" project inside. So that anyone (who wants to use my service) can reach out to the repository, grab Proxy project and adds it to his own project.
Does it make any sense? Is Proxy class really a part of the Service? or should it be build on the client side?
My second idea, was to create a "Samples" folder, and put Proxy project there.
A Proxy is a client-side representation of a service, so it belongs conceptually to the client, however, you as the service developer, can provide an implementation (or a code skeleton, or tools that can generate an implementation) for the clients to use if they want (e.g. they may not care about the details of the communication protocol, or caching, etc., and your proxy may handle some or all of that for them). In that case, they may treat it as a 3rd-party component, and may wrap it into an Adapter to change the interface to suit their needs, and reduce coupling to your service.
