Matching sending Virtual File with the returning EERP/NERP
From the issue #55 (closed) the sentence below has arose this problem. The object passed in the {{OftpletSpeaker}}'s sending file methods ({{onSendFileXxxxx()}}) is not the same instance provided by the {{OftpletSpeaker#nextOftpObjectToSend()}} method. The reason is that the framework needs to normalize the Virtual File with protocol's specification range of possible values before transmitting.
??"I currently need this counter to be correct to match the message that is sent and the EERP/NERP that is received."??
This is only possible because, internally, the API framework use the {{NormalizedVirtualFile}} interface to keep the {{OriginalVirtualFile}} reference. Instead of passing the original Virtual File on {{OftpletSpeaker}}'s sending file methods the change proposed is to use the {{NormalizedVirtualFile}} instance. So, users will be allowed to cast the {{VirtualFile}} into {{NormalizedVirtualFile}} and retrieve the original Virtual File when necessary.
An obvious example of the matching problem against the sent {{VirtualFile}} and the returning EERP/NERP is the {{VirtualFile#getTicker()}} property advised to be set automatically by the API's framework.