Communication threading model and (a)synchronization

[bluecmd]

There are a lot of potential functionality that currently is not supportable due to the synchronous implications of the library.

• All communication right now are realistically targeted to a single ComID as that is what I have seen in the real world on real drives.
• Implementation of e.g. method calls are IfSend followed by IfRecv towards the single ComID, which can conflict with multiple sessions being active on the same ComID.

Right now we have MaxSessions=1, we use the Synchronous protocol, Asynchronous=false, AckNak=false, BufferMgmtSupported=false - so realistically we will not run into any issues under these circumstances. Thus, marking as an enhancement for the future.

Right now I will ensure that we only use the maximum allowed sessions from the TPer - which seems to be 1 in the cases I have seen so far.