>So, current phone call?
>
>>Say, I spent up to this time from the morning still thinking of a good name instead of already working and coding. All my colleagues suggest 'CurrentCall'.

No, not phone call, the InvokeCall.

Here the words "invoke call" are used very often, so it's something we're all familiar with. That's why my colleague thought of the 'CurrentCall'. Even if I don't like it, within our software it's OK and everyone will understand what call we're talking about - it's essentially passing method call from one application to the other.

We can consider C++ application as interface and our .NET application as business tier since it implements logic for each such call.

Say, right now I am working on a Booking class. It was originally assigned to another developer, but I volunteered to implement it.

Anyway, one of its methods I am currently testing is 'Schedule Booking'. So, C++ will pass "ScheduleBooking" as a function and .NET application will do all the needed logic and will pass the result back to that application.

So I want an object to associate with each Invoke call. And this is the object I have troubles naming.

As I understand, you also don't like CurrentCall (at least the word call).

Originally I had this object named application but it is not what it supposed to be doing, so we need to rename it.