jauto

Big news this week!

Psi patch submitted!

I consider this subproject finished, unless JEP-0070 evolves in some unexpected direction (yes, still no final version containing required changes)
more »

jauto daemon 0.1 released!

Yes! Released! Still some changes are needed, but at least you can play with it.
more »

Plans for next week

• Apache module

Yaaaaaaaay! Exam passed! Happy happy!

Now, more on-topic news:

Work on XMPP Component is going really well. Yes, it is still unfinished, but… If you check my old schedule, there was one week planned for XMPP Component and one week for integrating XMPP Component with Apache module. Honestly, now it looks like XMPP Component will be a something like a server for confirmation requests, and Apache module will be a simple client (you can do authentication in Apache by checking user passwords in a file: this will be the same, but I’ll be “checking in” XMPP Component). So right now I have to put more efford into finishing the Component, and then Apache module will be really quick and easy.

While testing XMPP Component together with my modified Psi, I found a really annoying bug in my psi patch. And it took me all evening to find it. Hmm… Handling of element namespaces in Psi is really tricky… and honestly I’m still not sure what is going on there… but at least I found out how to fix my problem.

Plans for next week

Two main points:

• Submit Psi patch
• Release XMPP Component

Someone could say that I’m getting behind the schedule. The truth is that I’m dynamically changing the schedule, because I have to. I’m taking days from last weeks of the old schedule, from “documenting and packaging” time slot. Why? I noticed that it’s not a good idea to wait to the very end with releasing everything. Especially with Psi patch. Why? Because Psi is changing so much now, that even waiting few days makes it hard to merge my patch with the mainline. So I need to finish documenting the code in my patch now (as required to submit a patch to Psi) and try to get this into mainline ASAP. If I don’t spend a day or two on this now, I’ll have to waste all week at the end of August rewriting the patch to work with latest mainline.

Other plans:

• Jabber SoC Conference on Tuesday
• Mid-term meeting with my mentor on Thursday
• Start Apache module (if time permits)

As you can see, I managed to set up something that looks like a project website

Other news: Psi patch is 90% done. As a side effect, I improved stanza error handling in Psi
Since error handling will be probably a bit modified before including in Psi mainline, I’d like to wait for the official version and then create my patch, so it can be easier applied. If, however, this takes much time, I’ll release a dev-version of the patch.

I also did some research on Apache modules for authentication.

And I’m in the middle of getting in touch with JEP-0070 original author to get his help.

Plans for next week

XMPP Component

let’s have some fun with Python!

preparing for exams at univ

why? oh why?…

As I announced on Psi-devel mailinglist:

As a side effect of my SoC project, I improved stanza error handling in Psi (or rather Iris).

I did much work in Stanza::Error class. First of all, now it has fromXml()/toXml() members, so you can easily create error element:

QDomElement e = createIQ(client()->doc(), "error", jid, id);
Error error(Stanza::Error::Auth, Stanza::Error::NotAuthorized);
e.appendChild(error.toXml(*client()->doc(),
client()->stream().baseNS()));

Secondly, I added error mappings based on JEP-0086. This means that now Psi can read both old and new style errors (including error text, so no more empty “Reason: ” message boxes).
To make it more funny, if there is no error text at all, you can get default error description from RFC.

Other thing: some of error message boxes in psi have formatted text (”<b>”, etc), but had “\n” newlines, which don’t work in formatted mode. I changed them to “<br>”.

You can pull these changes from Darcs repository located at http://machekku.uaznia.net/darcs/psi/
Patches:
1. Improved stanza errors handling in Iris
2. Fixed formatted error message boxes

BTW: While testing my changes, I found a bug in Disco dialog.
To reproduce: try browsing a new server (like jabber.org) using Agents protocol. In old Psi, you’d see error message. In new Psi, you don’t get any message.