Re: [P2pim-devel] What to do next

[James H. <hol...@ke...>]

Forget the ID number. Control can give the GUI a File object when it begins a 
transfer. I'm thinking of queueing ID numbers because the user might want to 
send multiple files at once. To do this the program has to keep track of what 
files it's offering. We could send File objects back and forth, but it would 
be more efficient, and probably less dangerous, to use an ID to identify 
files.

An ID for the group is ok right now. After thinking about it I realized that 
using different group addresses and ports doesn't increase security or reduce 
bandwidth usage. It would decrease the work that the client has to do, but I 
don't think we're going to be saturating the CPU any time soon. The other 
options won't require a protocol change either, so they can be easily 
implemented later.

I think a user profile will just be a string object in the user object. It can 
be arbitrary data, as far as I'm concerned. The UI can create it and 
interpret it however it wants.