Frenchies speaking english... ouch, I didn't understand half of what you said
... :p (don't take it badly please)...
anyways, billiob, don't worry, I know it was a quick and dirty code to make it
'work' and as I said, I know it's not finished... I also
very much like the email idea, but n00bs will get lost, so it's better to have
it in the CW... and the perfect thing would be to have both
implementations and an option to choose which one to use! :D
About asynchronous, yes, there is a way, we only need to add a -command option
to the SOAP::create call, but I didn't test it and don't
know how it will work, will it receive the whole dump or just get notified, or
whatever.. it only needs testing, that's all.. anyways,
there is a # TODO on every SOAP call that says 'needs to add -command for async
call..."...
KaKaRoTo
On Sun, Sep 10, 2006 at 02:05:50PM +0200, Philippe Valembois - Phil wrote:
> I never said you didn't followed what I said :p
> I didn't see that Tom proposed the same thing ;)
> Phil
>
> Le Sunday 10 September 2006 13:56, Boris Faure (aka billiob) a écrit :
> > On 9/10/06, Philippe Valembois - Phil
> >
> > <[EMAIL PROTECTED]> wrote:
> > > I suggested to Billiob (who written the current GUI) to use the
> > > ChatWindow like we do with Mobile Messaging
> >
> > You told me that once it was done !
> >
> > > Le Sunday 10 September 2006 11:29, Youness Alaoui a écrit:
> > > > Thanks Tom, I fixed it, it was a typo I think....
> > > > btw, I just saw the code for OIM_GUI and it's bad... first, we don't
> > > > sort by sequence number, second, we do a getOIMMessage once to fill in
> > > > the titles, then we do a second getOIMMessage to read the message...
> > > > this means two SOAP requests (whih can take time for slow connections
> > > > and *may* freeze aMSN...)
> >
> > Yes, you're right.
> > I've done this way because "foreach {from nick MsgID} $oim break" was
> > not working fine for me.
> > That's why i've added a "getOIMMessage" to catch the nick and the email.
> > Plus, i wanted to get the sequence number in the first $oim, but it's
> > not there, which is strange.
> > Anyway, that code is bad and anyone who want to improve it or remove
> > and code it better is always welcome.
> >
> > > > about the sorting, it's not a problem because for now, I know the code
> > > > is still new and it's not yet written... but about the 2 SOAP requests,
> > > > it's bad, because you'd better design it correctly from the start...
> > > > Also, like Tom said in the forum link below, maybe it would be better
> > > > to show the OIMs in the chat window, because people might get
> > > > confused...
> >
> > I think Tom is right but i didn't mind that feature this way, but like
> > emails.
> >
> > Greets
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
