WHAT to port and WHAT not to :-
###Hightlights of the current mailman.client :
_Connectionclass handles all the request making.
Clientclass is the frontend for the user. It provides properties like
- There are classes such as
_Addresseswhich are utilised by
_Useri.e which are not directly used by the
###Proposed port :
- In the new mailman client the role of
Clientclass would be the same. It would do talking to the user. So, it is not required to port this one physically ( I mean not techinally i.e we have to port it to JS though :-) ).
- In case of
RequestAclass is proposed which will do
mailman-coreand will implement Promises and Callbacks. This
RequestAclass can be further subclass to add further functionality to have a class
- The classes analogous to
_Domainsand others will behave the same as in mailman.client but they all will inherit
RequestB. This will facilitate dynamic request object building by using the chaining syntax.