MSNp14 status?

[Evan Schoenberg]

On Jan 30, 2008, at 4:16 AM, Ka-Hing Cheung wrote:

> No, it's not an accurate reflection of the status. Currently there's
> msnp14 which is in i.p.p, then there's msnp15 in a branch. Both code
> bases do not renew the cookie/token (msnp14 doesn't even try, msnp15
> tries, but not correctly), so soap actions will eventually fail after
> you are logged in for a while. For msnp15, the "a while" is at least 8
> hours, so it's less a problem for that branch. It should be pretty  
> easy
> to fix the msnp15 side.

Is there any reason for msnp14 to continue to exist in i.p.p, if  
msnp15 is the focus of what efforts currently exist?  Would it make  
more sense to move msnp15 to a disabled-but-in-i.p.p status?

> Another problem that people seem to encounter is ADL failures. I  
> suspect
> this may be because of some buddy list out of sync issues, but I  
> have no
> idea at this point. Do people still get 1000 dialog prompting for sync
> buddy list these days?
On msnp14, I don't know.  On the current msn prpl, they definitely do.

-Evan