I’m leaving tomorrow for Las Palmas de Gran Canaria.

I was lucky enough to be sponsored by the GUADEC travel committee! I’m thrilled to meet some great new people.

Sorry for the late post everyone. I’m prepping to fly to Gran Canaria tomorrow for GUADEC. (Early, I know).

this last week was filled with other work and planning for my own project.

I have a finalized idea of how the service back end will track lists.

It is unlikely that I will be using Twisted for my server connectivity. Instead, I am currently using GNIO through pybank / girepository.

Twitter-esque entry #241011: Investivating Twisted for asyncronous connection directly to IMAP

I have successfully modularized my code. My DBus API now has little trace of IMAP-ism and my cache is working fully asyncronously. It has been a week of learning. Being asyncronous was hurting my brain initially. I’m getting used to it.

This past week:

• Fought with Git
• Cleaned code
• Separated code into module files
• Fetch data using UID instead of IMAP folder sequence number
  • This will be useful for when I’m not dealing with IMAP-based mail
• Fetch mail from the local cache if it is present, otherwise, ask the server
• Started code to enable the fetching of specific mime parts from a message

That’s about it for this week!

Little progress this week, unfortunately. Some unrelated work got in my way.

The last week was spent discussing how I want to have the DBus API and the storage backend communicate.

My TODO list was:

• DBus API needs to be totally independent of the cache
• Store raw RFC822 messages in a Maildir-esque local cache

Information requested of the DBus objects will send the request through to the storage backend which will now search for it locally but hit the server if the required information is required. This is rudimentary at the moment.

I started coding during the community bonding period.

During this phase I laid out the DBus API for mail, started a basic Command module that will control configuration data. Mail will be broken down into objects.

Most of this time was spent figuring out how to handle asynchronous requests of the mail server. Initially, I am using a bunch of threads and a queue for them to pull work from.

Thunderbird has my Funambol plugin so I can sync with my Blackberry. Evolution handles signatures in a way that I agree with. Thunderbird looks nicer. Evolution doesn’t need to be told to fetch messages from all of my IMAP folders Thunderbird has superior message threading. Evolution is a Gnome app. Thunderbird can mark messages deleted, instead of moving them to some weird Trash folder. Thunderbird doesn’t have the ugliest default addressbook of all time.

So, coding has officially started. I have some code written already.

Right now, I’m working on getting a cache controller written. Requests will handed to the Account object, which will then dispatch the actual requests to the Cache controller.

The Cache controller will search locally for the message or hit the server if necessary.

https://desrt.ca/gitweb/?p=marcinmail;a=commit;h=5b8919335c7170fb086abffb93336237dc08f2a6

See title.

He would be better to explain it.

Working on the idealogical hierarchy of the API now.

Account
└── Folders
  └── List
    └── Message
      ├── Headers
      └── Message Parts