>>Hi everybody,
>>
>>I am wondering what principles do you use when naming classes (and their methods / properties)? Do you know a good article on this topic?
>>
>>Say, right now I am thinking of how to name a class. My colleague suggested to use 'CurrentCallObject' for the class name, but I am not sure I like it. On the other hand, I don't have a better idea.
>>
>>This class is going to be instantiated on each invoke call (this call comes from C++ application) and will hold attributes related to the call.
>>
>>Thanks in advance.
>
>Current for a class does not makes sense to me, current will be an instance of a class, for example CurrentRecord (an instance of the class Record, which happens to be the current one), LastRecord (an instance of the same Record class which happens to be the last record) etc
>
>Call does not makes sense to me for it introduces ambiguity and in the end we do not know what you are using the object for.
>
>What about using a Bridge idea, as you are building a Bridge between the two applications.
>
>CppToNetBridge or CppTo{Name of your Application}Bridge or {Cpp application}To{Name of your Application}Bridge
>
>Now the instance of such object could be named after the name of the Cpp application, for example Current{Cpp Application Name}
>
>I do not know, just a quick thought on it.

Thanks, Hugo. My colleague just posted a new list of proposed names which I like much better.

Class name suggestions:
Call
Request
MiddlewareCall
MiddlewareRequest
InvokeRequest

Instance variable names:
CurrentCall
CurrentRequest
CurrentMiddlwareCall
CurrentMiddlewareRequest
CurrentInvokeRequest