So, last week was the last one to be so unproductive (for my GSoC project of course). I already started to implement the Iris Jingle tasks. It doesn't go as quick as I wanted but, that will get better.
Here's how I'd like to implement Jingle : On the Kopete side, we have a JingleSessionManager which... manages all Jingle sessions. This manager will have a graphical interface or the chat window will get the events from it or both, that doesn't matter that much for now. It also will be the path between the media manager (what manages audio and video) so the 2 parts are totally managed separately. On the Iris side, the JingleSession will be a class which collects all needed informations and start a Jingle task to establish the session. A first information collector is the JingleContent class. As a content tag in Jingle can have lots of different behavior, this class gets all needed informations for one content type and make a QDomElement containing the content tag to give it to JingleSession and the Jingle task. Kopete will start, modify and/or terminate the session only with the JingleSession and shouldn't have to use instances of any Jingle task. That is for sending an initiation request. When an initiation request is received, the Jingle task negotiate and establish the session, then give a JingleSession instance to Kopete so it can be used to modify or terminate the Jingle session the same way it is done in the other direction. Anyway, some little things are not quite clear : * I don't want to use a Jingle Task in Kopete and let the Jingle session manage it itself when I send an initiation request but when I receive an initiation request, I have to use that Task in Kopete code (That Task is always present waiting for a jingle initiation request). Wouldn't it be better if both direction worked the same way ? A Task and a Jingle session for both directions ? * I think that creating a Payload class and a Transport Class, etc... would become too much. That's why, currently, the payload-type element must be directly added in the form of a QDomElement. I don't know if it is good or not. Cheers, Detlev Casanova.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
