I’m publishing imapfw, a new IMAP tool which I intend to replace OfflineIMAP. ,-)
- A call for feedbacks
- How it looks
- A brief introduction about imapfw’s internals
- Final note !
Some months passed since my previous announce to make a deep refactoring of OfflineIMAP. While doing this job, I realized it was something very hard and it would be better to write a new software. That’s what I’m currently doing and it’s called imapfw.
This tool won’t do much for now. This is still in very early development stage.
Because it’s WORK IN PROGRESS and EXPERIMENTAL stuff, it won’t make anything good. Expect it to have strong failures.
Here are the main goals I have in mind for imapfw:
- use the last Python 3 technologies;
- clean and beautifull code;
- easily extensible;
- fully (aggressively?) concurrent;
- fit the needs to both novice and experts;
- support a lot of use cases;
- safe and with embedded unit tests;
- fucking good documentation;
- IDLE mode? I’m still not sure about this one.
Believe me, those goals altogether are very ambitious.
That’s why I decided to make imapfw a framework (hence the name imapfw) which I want both simple and powerfull.
Beginners shouldn’t be scared, though. All the framework architecture only requires ONE file which is called the rascal. It won’t require the user to write one line of Python code.
A call for feedbacks
I’m publishing this tool today in order to get your feedbacks. Any constructive comment is always welcome but keep it in mind this is WIP, please!
Also, feel free to give your opinion about anything.
Users of OfflineIMAP
Since I intend imapfw to replace OfflineIMAP in the long term, you might want to follow the development and give your feedbacks. My best guess is that you will mostly be interested by the rascal: how it looks, is it hard, etc.
This call for feedbacks is mostly for you! Please, do fork the project and read a bit of code. Early feedbacks about code are very important.
I don’t expect patches, for now. However, let me know if you’d like to contribute soon. I’ll share more about what I have in mind.
How it looks
This section is partially obsolete.
A good start is to fork the project and look at the CLI options:
The main argument is the
ACTION. It tells what imapfw must do. I’ve started the implementation of the most expected feature:
syncAccounts. For now, it won’t sync anything and you can run it safely.
Here’s an extract of the rascal:
- The first thing to notice is that configuration options are dictionnaries. Forget the INI style. I aim simple users to not have to write ONE line of Python code.
- OfflineIMAP users should feel comfortable reading this file. It follows almost the same semantic and the same logic around accounts.
- Most experienced users will notice the classes. Here is the hierarchy and how
they are logically linked:
- an account is defined (derivates from
types.Account) with both
- a “repository” (I’m about to fully remove this term) maps to a configuration dictionary and a driver to actually access it. It derivates from the associated type (
types.Imap, etc) and the drivers are similar (
- an account is defined (derivates from
On top of this, each type acts as a controller for the underlying driver. I expect experimented users to make most of their “crappy” things^W^W tuning here. ,-) Think about filtering folders, nametrans, etc.
How everything is linked is important: it’s possible to decide what type uses which driver for what account.
Now, look at the imports:
- actions are the actions available from the command line.
- engines allows to define the default engine to use for the action (if this action supports more than one engine). It can be redefined at the CLI!
- types are the little sisters of the OfflineIMAP’s repositories: Maildir, Imap, Gmail, etc, in the sense they hold a driver and some configuration options (like the credentials) to access it.
- drivers are the low-level drivers to use for the types (didn’t exist in OfflineIMAP).
The imports are what makes the framework so powerfull. They allow users to redefine the default behaviour, or even write their own new full backends.
Because actions, engines, types and drivers are well orthogonal and distinct concepts, extending imapfw should be much easier than it was with OfflineIMAP.
A brief introduction about imapfw’s internals
Internally, there are other implementation concepts that some of you might like to be aware of. The most important are the concurrency, the workers and the managers.
The concurrency is a module to use a single and very simple API whatever the Python backend in use (
threading). Yes, I’m aware they are already very similar but they still have some subtil differences it’s better to avoid introducing in the long run. We force using a subset of them.
Because the conccurency backend is easily switchable, worker is a simple term to refer to either a process (
multiprocessing) or a thread (
The managers are objects to nicely handle concurrency. It takes inspiration from the managers of the
multiprocessing library. They allow to have an intuitive usage for the “passing by message” design.
Final note !
It’s time for me to write the last words. I’d rather let you to discover imapfw more in details by yourself.
This post is long enough for today! Also, I’m getting very tired (I ddin’t sleep this night to polish the code, publissh it and write this bloog post). I hope nobody have noticcce…. :-D