Task #124043 has been updated. Project: aMSN Subproject: File Transfers Summary: File transfer protocol used is not always the good one Complete: 100% Status: Closed Authority : kakaroto Assigned to: vivia
Description: When we send a file transfer invitation, we always use the same protocol (depends on whether user enabled the 'use new protocol' advanced pref. Some users still have windows messenger or some other clients that support only one of the protocols, we should make sure to send the FT transfer invitation in the correct protocol depending on the other user's clientid and capabilities. Follow-Ups: ------------------------------------------------------- Date: 2006-04-08 20:01 By: kakaroto Comment: we need to check the clientid, if there are NO msncX fields set, then we know the user doesn't support the new protocol. I suggest having a new proc clientIdHasMSNC that would do a binary and, and check for all the fields at the same time, instead of an if msnc1 && msnc2 && msnc3 ... ------------------------------------------------------- For more info, visit: http://sourceforge.net/pm/task.php?func=detailtask&project_task_id=124043&group_id=54091&group_project_id=46366 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
