Add ETCP, LUDP and GUDP strategies support

[gioblu]

Ciao @Girgitt following through the issue opened by @drtrigon

Would be nice to have ETCP, LUDP and GUDP support.
Do you think it could be possible to pass the strategy as an option?

Could an arg be passed containig a symbol or a string specifying a certain strategy then used here?

Could the Any strategy help here, abstracting the strategy (no need to know it at compile time) see example

My compliments for PJON-piper and thank you for your feedback, support and passion.

[Girgitt]

Hi @gioblu I was thinking about exactly the same - how to add operation mode (including strategy selection and associated options) in a clean way. The new branches naming convention supports compatibility-breaking changes in args and stdin/out interface and would use that.

I made some of the branches while fixing compatibility with PJON but changes which would enable specifying strategy would need the PJON-piper API designation to change from 0 to 1 and would be possible in dev-1-11 branch which does not exist yet (I need to design better options and stdin/out interface first)

[gioblu]

Ciao @Girgitt versioning seems extremely well organized.
I agree with you that strategy selection would make PJON-piper extremely flexible and useful.
I am sorry if I have generated additional complexity in versioning and thank you for reporting the breaking changes.

[Girgitt]

No worries @gioblu - you have not generated complexity in versioning - I did this earlier (before discussion on strategies even begun) to prepare for future changes and to keep PJON-piper, PJON-python and PJON synced with the pip versioning of PJON-python. Too bad I recently begun implementig redis proxy directly in esp8266 making PJON-python less critical for now (It ised to be my proxy between PJON nerwork and redis) and waiting for its turn to receive a final update implementing the above versioning scheme..

[gioblu]

Ciao @Girgitt thank you for your feedback, keep up the good work.