move transaction handling into framer socket.

[janiversen]

Transactions at device level is only supported by the socket framer, therefore it is logical to remove the general transaction handling, and make a specific transaction handling directly in the framer.

Seen from the APP POW, the library offers a request/response API, meaning there are never more than 1 transaction outstanding, so need for a app level transaction handling.

The request/response API is partly not protected by a lock, making it difficult for multitask application to secure serialization.

• for sync clients, no further lock is needed (apps using threads and sync calls, need to manage this themself)
• for async clients an asyncio.lock needs to be added to all calls (centrally in the execute), important the lock needs to be reset in case of exceptions.

This should only be implemented in the new framers, and the old_framers kept unchanged.

[janiversen]

Correction the server still needs to know the transaction id, but since the server handles the requests one by one. the socket framer can keep the tid from the request and automatically add it to the response.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[janiversen]

It will be done differently, in the new transaction layer.