From: Alistair Y. <ali...@sm...> - 2006-07-11 15:00:50
|
> the trouble we had > persuading you to even *try* MSN for the ASK project don't I know! all that crap about your bank balance, when is a convenient time to open your system for hacking, hope you have a nice day, welcome to msn ;) I had to bin my chat client to use msn I'll have you know. The fact that I chose a better client all round is neither here nor there though. I could have stuck with my jabber account if I'd dusted off my "python for scarred bod developers" and put in the jabber/msn gateway for wildire. But in the end I thought, why bother standardising? just use the right tool for the job. That's what users like to do. So just support them doing it. They can use their chat client of choice as everything is server- side. The Rosters (buddies) are all created for them on the fly from the SRS so when they login using any client they care to, they'll instantly see who's online, in their learning groups. The subscrptions are taken care of by policy and some nifty coding ;) In fact, when someone new enrolls on their course and they're online at the time of enrollment, they'll see a new buddy appear in their list! So what we want to do is have a bod view of what the client sees. Could use the Smack API but you need their password, which isn't in bod. Pity, as I can't wait to call the app SmackHead! Alistair On 11 Jul 2006, at 15:48, Peter Crowther wrote: >> From: Alistair Young >> Why don't they just use their client in the first place? > > Because there is no standard chat client, in the same way that > there is > no standard document format. I'm sure you recall the trouble we had > persuading you to even *try* MSN for the ASK project, Alistair! > > One can standardise on a server and allow many clients, or on a client > and allow many servers. If you can't assume much about your client > environment, as is typical with e-learning, you have to standardise > on a > server - and coincidentally produce Yet Another Web Chat system. > > There is a fix for this: aggressive standardisation. Standardising > early eases the deployment and implementation burden. However, > this fix > is possibly worse (for the human race as a whole) than the disease, as > premature standardisation slows down innovation and forces us to live > with poor or lowest-common-denominator functions. RDF and the layers > above it can be held up as a prime example in the Web world... > > - Peter > > > ---------------------------------------------------------------------- > --- > 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 > _______________________________________________ > Bodington-developers mailing list > Bod...@li... > https://lists.sourceforge.net/lists/listinfo/bodington-developers |