Re: Data messages
Rodney Dawes <[email protected]> Thu, 24 Jun 2004 12:47:43 -0400
| Newsgroups | gmane.network.everybuddy.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2004-06-24 at 17:21 +0100, Meredydd wrote: > CCing this back to the list, as I'm not the only one with an interest in > this (sorry, this list doesn't munge reply-to). Heh. Use "Reply to All" next time? :) > On Thursday 24 June 2004 16:19, you wrote: > > On Wed, 2004-06-23 at 13:01 +0100, Meredydd wrote: > > > On Monday 21 June 2004 03:03, you wrote: > > > > As far as I can tell from the GUI_SPEC file and the gui_comms.c > > > > file in src/, all that is theoretically possible with this, is > > > > the sending of data over a stream, not necessarily the attaining > > > > of data being sent to you, or arbitrary data that might get > > > > received on log-in such as the cookies from yahoo/msn. > > > > > > Indeed. Prod me! I'm working on an out-of-band comms system which > > > we could use for things like these cookies, and I'm trying to think > > > my way around password management. Possibly something which a > > > service plugin can call, which would obtain the password by > > > whatever means necessary and then call a callback. Do you reckon we > > > should do this on a per-local-account basis, or expand it to a > > > generic set of passwords, keyed to particular strings? And if it's > > > the latter, perhaps this should be linked to password fields in the > > > proferences? That might be a little nicer, really... > > > > I am not sure. Something similar to how basic auth with HTTP works > > would probably be good. > Umm...what do you mean by that? HTTP Auth is a crummy model, in my > opinion, because it's designed to carry authentication over a > request-based protocol, with the wrong party (the client rather than > the server) initiating... I meant the Domain/User/Password model. The eb-lite protocol is no less of a request-based protocol than HTTP is really. And the server initiates the authentaction (it requests it from the client, when the client has requested a url that requires it). But that's neither here nor there. > > > > What is the plan for handling that > > > > sort of stuff? It would be nice to start getting some of that > > > > done, so I can do some neat little things in Senility with > > > > regards to integrating in the Gnome desktop. > > > > > > > > Such as plunking buddy icons into the address book for contacts. > > > > > > Now that would be neat > > > > Indeed. It is neat. > Hmm. Incidentally, what do you need from the core before you can do > that? The UI needs to be able to get buddy icons. Once I can do that with eb- bite, I can put them in the senility buddy list, and add the code to integrate with the evolution-data-server address book stuff, and put the contacts with their buddy icons, in there. -- dobey