[KMess-devel] Trying to implement the first part of MSNSLP in master

[Sjors G. <sj...@sj...>]

Op 25 mrt 2011, om 07:05 heeft Adam Goossens het volgende geschreven:

> On the P2P side, I've been able to wrap my head around a lot of the
> concepts as well so if you want someone to bounce ideas off, let me
> know.

Hi Adam and rest,

So _everything_ regarding msnslp, file or display picture transfer is gone in master. We're going to have to start from scratch here, which is a good thing, because now we can do it in a more structured way using the msntransfer library by Gregg.

However, I'm afraid to actually start, as I don't understand the whole picture, probably until I've implemented it all. Therefore, I've copied the KMess Echobot into a seperate directory called the "MSNSLP tester" (it's in the kmess-bots repository on Gitorious). I intend to try to implement most of MSNSLP *inside* this bot, and have it all working, before I start gradually moving things into the library itself. I hope this will enable me to make more mistakes, to see the big picture before I modify the library, and to have an easier testing bed. Of course, I would like your help (your=all of you) while starting to implement things.

First of all, I think I'm going to implement invitations. I've looked through msntransport and the MIME type for invitations is nowhere in there, but the invitation keywords "INVITE", "BYE" etc are there. I think the complete SLP dialog is in msntransport/src/msnslp/dialog.h, but I don't know what layer this is; the dialog is built up of Transactions which the msnslp bot can create itself. So if, for every chat, the msnslp bot keeps track of a list of dialogs, would that be a good way to start this?

By the way, the msntransport library is built around a Platform singleton, which we don't want considering the library shouldn't use anything that's static and non-const. So, I think we should remove the const-ism in Platform, and create a Platform per msnslp bot and eventually, per library instance. Agreed? (As far as I can see, there's no reason to have the Platform as a singleton, except it's easier to get to the object if you know you just have one...)

Sjors