[bme-develop] P2P code

[Sir M. <obe...@ho...>]

Hi guys,

a quick update from me! The status code is now working fine and I'm 
currently working on adding group support to Bme. I do have a question about 
that...what I want to do is the following, I want to make an object 
ContactList that contains all the Contact Objects along with the groups send 
by the LSG command...I will make this ContactList archivable so the list can 
be cached! Do you have any idea where I should put this class? I think the 
cleanest way of handling the caching of list+ user info will be by letting 
the BmeApp class write it...any other/better ideas? btw automatically loggin 
in is broken now in the CVS version, but will be functioning again when I 
add the cache code!

I also have been reading up on the p2p protocol:
>Right now it has no use. We will need it to create msn Objects tags
>once we introduce user display pictures and custom emoticons. So far
>Bme only stores msnObjects from the contacts in your list, it doesn't
>create one for the user. To update you on getting display pics, Bme now
>is able to send invitations to request your conversation buddy's
>display picture, so far the only response I get is 500 Internal Error,
>this means there is something wrong in the invitation, I believe the
>problems is in the msn Object encoding but I haven't been able to
>figure it out.
>
Ok you probably found this out already, but in case you haven't, I'll state 
the obvious. Zoronax' site gives the following causes of a 500 Internal 
error:

#  Incorrect "Content-Type" field
If the message you received contains a "Content-Type" field with an type 
which is not supported by your client, you should reply with a "500 Internal 
Error" on the Status-Line. The value of the "Content-Type" field should be 
"null" and it shouldn't have content, so the "Content-Length" field has 
value "0".

# Incorrect field(s) in the Message Body
If some fields in the Message Body contain a value you don't agree with, you 
should also reply with a "500 Internal Error" on the Status-Line, but the 
value of the "Content-Type" field should have the same value as the received 
message. The Message Body should now only have the field "SessionID" with 
the Identifier of the Session as value.

So if you look at the content type you'll be able to determine which of 
these two errors you get in response....if it's null it's the first one, if 
it isn't it's the second....any idea which of these two errors it is?

oh btw...Daniel is your p2p code in CVS? (make sure you make a backup from 
your old code before checking out cvs, just to be sure...I don't know in how 
far my code breakes stuff....but lots of things have been changed!!!!)...if 
you upload the p2p code commented I can have a look at it too!

regards,

Tim

_________________________________________________________________
Talk with your online friends with MSN Messenger http://messenger.msn.nl/