On Sat, Oct 25, 2008 at 02:09:54PM +0200, Boris Faure (aka billiob) wrote:
> On Sat, Oct 25, 2008 at 13:23, Vivia Nikolaidou <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I think MSNP16 and MPOP is pretty stable now. I've been using it for
> > several days, I've also kept two PCs connected at the same time, it
> > worked fine after KKRT's fix for messed-up CW titles. The only
> > problems are:
> >
> > 1) We don't have roaming DP implemented yet, so if you keep two
> > different DPs on the two clients connected, the one that users will
> > see is the one of the client that last changed status.
> > 2) When we open a SB, we probably also need to invite our other "self"
> > to join, otherwise the conversation will only be on the side of the
> > client that initiated it.
> >
> > Maybe we can have P16 on by default for 0.98? What does everyone think?
> 
> When are we releasing 0.98? The main issue with enabling P16 by
> default is that it's not currently used in any stable wlm version, but
> they shouldn't change the protocol...
> Moreover, we should fix those 2 issues before enabling it by default.
> 
> 
> -- 
> Boris FAURE (aka billiob)

My plan is to release 0.98 in the coming weeks.. we already
talked about that on IRC, we said that we would release 0.98
once libnice/farsight2 are released!
And just so you know, I'm releasing libnice TODAY! :)
so get ready to do some bugfixing! there are a lot of
interesting things to take a look at in the wiki (Forums
TODO page) which should be fixed before the release...
I suggest we disabled spaces support since it's not that
'good' yet (unless someone wants to work on fixing it once
and for all!) then we're ready to release 0.98 RC1!!! or
maybe we should just release it as 0.98, then leave the
bugfixes to 0.98.1, etc... 
We should probably change our release methods...
Also take a look at the bug tracker because most of the P15
bugs are in there.. and I think we should wrap every $ab or
$sso or $roaming by calls that would make sure the vars
exist!
for example, instead of :
$sso RequireSecurityToken ...
We should do :
::MSN::SSO RequireSecurityToken ...
and have :
proc ::MSN::SSO { args } {
   if {[info exists $::sso] && $::sso != "" &&
       [catch {$::sso info vars}] == 0 } {
      eval $::sso $args
   } else {
     set ::sso [SSOAuthentication -user .... -password ...]
     eval $::sso $args
   }
}

Some for the addressbook and roaming objects...

KaKaRoTo

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to