Add `Azos.Client.IEndpoint.SetDistributedCallFlowBlock: bool` with ability to default caller agent etc from Endpoint name

[itadapter]

Related:

• 846

[itadapter]

Need to discuss if this feature is needed. DistributedCallflow introduces network and processing overhead. It is only needed in some cases, like establishing the lineage , however the server must be able to make sense of the call information otherwise passing extra headers is senseless. While its true that any endpoint may benefit from it, the server side must be able to use the passed info (e.g. log it).

Also call flows are used for director identification. On behalf of what MAIN activity (director) does the call take place? Once again, to make sense of it, the server must be able to respect the director. Shall the client pass director through? There are many questions here.

[itadapter]

The verdict is: must start DCF explicitly. No property needed

• Distributed call flows are expensive
• They require server site coordination
• And client site coordination, e.g. use of REL guids in logging (otherwise they are sensless)
• Therefore: you must start DCF manually. Use DCF.ExecuteBlockAsync(...)