I apologize if this is a little vague, but I'm curious about what most people use for naming conventions for classes that access a webservice. Typically on my team we create separate projects for BLL (business rules), Model (DTOs and ASP.NET model classes), and Data ( typically Db and WS I/O ).
My question is in regards to what teams do for classes that access services. Typically in our Data project we postpend 'Dao' to the class name that queries the objects in the Db. So for example a class that does CRUD operations in a Db on Foo objects we typically name FooDao.cs and there seems to be general consensus on the team for that pattern. But what do teams do for classes that query webservices? Sometimes we name them as FooFacade.cs, or FooSvcClient, or even FooSvc.
I understand there probably isn't a true right or wrong answer here, but I want to know what others do, and if there is momentum towards a particular approach.