[gdm-list] GObject branch

["William Jon McCann" <mccann jhu edu>]

Hi,

Just a quick update on the status of the GObject branch [1] [2].

* D-Bus is now required
* The class design should be pretty much set.  It seems to work fairly well.
* The slave process management seems to work well.
* There is another reworking of the configuration framework.  It still
uses the same desktop file backend.  It is mostly done except for the
change notification stuff.  The new system works a bit like GConf
except the backend only knows strings - all typing and interpretation
of schemas occurs in the client.
* Simplified the XDMCP management even more by abstracting all address
details (GdmAddress).
* Reworked the md5 and cookie code.
* Added a new generic posix signal handling singleton.
* The SUP and SOP socket protocols have been removed in favor of the
separate configuration framework and the D-Bus object API.
* At least for now I've removed gdmsetup/gdmlogin/gdmphotosetup/gdmdynamic
* I don't think I'm going to continue to read the server
configurations from the configuration file but rather talk to HAL or
PolicyKit to determine what seats are available.  We should
dynamically create a display/greeter per seat.  XDMCP works as before.

At this point I've gotten the greeter to start on both static and
xdmcp displays.  But since the greeter control protocol isn't hooked
up logins aren't possible yet.

Next steps:
* Add caching and bulk retrieval to settings framework
* Rework the greeter control protocol.
* Hook the verify framework back up.
* Make it work.

Ray, I'd like to hear your thoughts on how to redesign the greeter
control and verify subsystems in light of your smartcard/threaded
work.

Still kinda in pieces but coming together.  Let me know what you think.

Thanks,
Jon

[1] http://svn.gnome.org/viewcvs/gdm2/branches/mccann-gobject/daemon/
[2] http://bugzilla.gnome.org/show_bug.cgi?id=376010