Fwd: Applying for a reimbursement to the Desktop Summit 2011

[Sjors Gielen-5]

Hi all,

FYI. About the hotel rooms. Don't forget to send them an e-mail soon if you want sponsorship!

BTW, about msnp2p: I'm working on an msnslp bot that will use the P2P messages from the library and the contrib/msnslp code to test whether I can get p2p to work. Eventually most of the code to make it will will go back into the library, but this makes it easier for me to test it. Now that both Diederik and Gregg aren't answering anymore, we'll have to find out most myself. I'll give you an update soon-ish.

Begin doorgestuurd bericht:

> From: Claudia Rauch
> The reimbursement policy for bigger conferences (and that includes the
> Desktop Summit) is that KDE e.V. usually reimburses 80% of the travel
> costs (in your case: the plane ticket) and a certain fixed amount for
> the accommodation. This time, we already arranged for a number of
> hostel beds which have already been paid for. These are only for the
> sponsored attendees. The hostel with those rooms is not listed on the
> accommodation page, as I will allocated the beds for the sponsored KDE
> attendees there.
>
> To sum up: if you get KDE e.V. sponsorship, I will book you a room in
> that hostel, and you don't need to worry about it.

Sjors

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
KMess-devel mailing list
KMess-devel@...
https://lists.sourceforge.net/lists/listinfo/kmess-devel

[Adam Goossens-2]

I won't be able to make it since I can't get the time off work unfortunately.

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.

On Thu, Mar 24, 2011 at 5:33 AM, Sjors Gielen <sjors@...> wrote:

> Hi all,
>
> FYI. About the hotel rooms. Don't forget to send them an e-mail soon if you want sponsorship!
>
> BTW, about msnp2p: I'm working on an msnslp bot that will use the P2P messages from the library and the contrib/msnslp code to test whether I can get p2p to work. Eventually most of the code to make it will will go back into the library, but this makes it easier for me to test it. Now that both Diederik and Gregg aren't answering anymore, we'll have to find out most myself. I'll give you an update soon-ish.
>
> Begin doorgestuurd bericht:
>
>> From: Claudia Rauch
>> The reimbursement policy for bigger conferences (and that includes the
>> Desktop Summit) is that KDE e.V. usually reimburses 80% of the travel
>> costs (in your case: the plane ticket) and a certain fixed amount for
>> the accommodation. This time, we already arranged for a number of
>> hostel beds which have already been paid for. These are only for the
>> sponsored attendees. The hostel with those rooms is not listed on the
>> accommodation page, as I will allocated the beds for the sponsored KDE
>> attendees there.
>>
>> To sum up: if you get KDE e.V. sponsorship, I will book you a room in
>> that hostel, and you don't need to worry about it.
>
> Sjors
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> KMess-devel mailing list
> KMess-devel@...
> https://lists.sourceforge.net/lists/listinfo/kmess-devel
>
>

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software
be a part of the solution? Download the Intel(R) Manageability Checker
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
KMess-devel mailing list
KMess-devel@...
https://lists.sourceforge.net/lists/listinfo/kmess-devel

[Sjors Gielen-5]

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

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
KMess-devel mailing list
KMess-devel@...
https://lists.sourceforge.net/lists/listinfo/kmess-devel

[Sjors Gielen-5]

Op 15 apr 2011, om 12:38 heeft Sjors Gielen het volgende geschreven:

> 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?

Apparantly, the things I've been seeing were invitations into MSNFTP. Is MSNFTP still used nowadays? I somehow remember it is old and unused, but KMess 2.0.x still seems to do it by default. I can implement it in the msnslp bot, but if it's useless to begin with, why bother. That's why I'm asking ;-)

Sjors

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
KMess-devel mailing list
KMess-devel@...
https://lists.sourceforge.net/lists/listinfo/kmess-devel

[Sjors Gielen-5]

Op 15 apr 2011, om 16:04 heeft Sjors Gielen het volgende geschreven:

> Op 15 apr 2011, om 12:38 heeft Sjors Gielen het volgende geschreven:
>
>> 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?
>
> Apparantly, the things I've been seeing were invitations into MSNFTP. Is MSNFTP still used nowadays? I somehow remember it is old and unused, but KMess 2.0.x still seems to do it by default. I can implement it in the msnslp bot, but if it's useless to begin with, why bother. That's why I'm asking ;-)

Apparantly, MSNFTP is _newer_ than MSNP2P, it's the currently preferred way. Both MSNFTP and MSNP2P are described on this page: <http://www.hypothetic.org/docs/msn/client/file_transfer.php>. MSNP2P is used as a fallback to MSNFTP and is still used either way for the display picture and other msnobject transfers (I think). So we should implement both, but with a slight edge to MSNP2P as it is needed either way.

MSNFTP is quite easy to handle. MSNP2P is where the msntransport library comes in. All application/x-msnmsgrp2p packets should be sent through the library. It will parse the P2P header, the SLP contents, and the actual requests and responses. Actual behaviour, such as file/msnobject saving, can happen by implementing EUF handlers (EUF = End User Feature). An interface (base class) for those handlers is in the library; you register them through the Platform and when you hand messages to the Platform, the EUF handler methods will be called.

I don't understand everything happening in the library, but this is the focus I will have implementing this the coming days. I will try to interface with the msntransport library for doing MSNP2P in the test bot, and once I reach a sort-of stable state where, for example, MsnObjects can be retrieved, I will start moving stuff into the library. Once it has pretty MSNP2P support, I will start adding MSNFTP, but the largest milestone will have been reached. :)

Please let me know what you guys think, any suggestions or ideas.

Sjors

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
KMess-devel mailing list
KMess-devel@...
https://lists.sourceforge.net/lists/listinfo/kmess-devel