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

While planning this project, I thought that it would be a waste to limit myself just to HTTP requests with HTTP Authentication. Just think how many of the sites you visit every day uses HTTP Authentication? And how many displays small user/password form and maintains everything in PHP sessions, etc? So I thought it would be nice to have a PHP function triggering all the XMPP-part if the protocol, without employing the HTTP Authentication headers.
Or why not to use it with your 3-python-line long HTTP server which you use to share files with friends?
Or something else?

And so, partially to make the above come true, and partially to make my testing job easier, I created a simple Python function + command line utility that triggers confirmation request and gives back the result.

jauto daemon 0.1 with command line request tool is coming later this week! First I need to kill some stupid bugs, I don’t want you to laugh too much while looking at my code

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)

Bad week, bad…
Bad in my personal life, but it was so hard, that it influenced my work and I didn’t do everything I planned, sadly. But fortunately all the bad is gone now, and I could grow stronger!

XMPP Component is.. hmm… 50% complete. I still need to add some request handling logic, but it should be fine really soon.

Plans for next week

Finish XMPP Component

More Python fun!

Prepare demo for mid-term evaluation

Next week, I need to show my progress to my mentor. Got to finish and polish unfinished things!

Exams at last!

Aaaaaaaa!!!!