> Lower Priority > -------------- > Entrance: > * XDMCP On the subject of XDMCP support for entrance, I am looking at how xdm does it, and it seems the logical way. How much structure/code can we reasonably pinch from them (both under licensing restrictions and people's sensibilities), or do we have to re-invent the wheel?
I mean, it would be feasible (from a coding point of view) to just rewrite a few callbacks and dump a load of the files into CVS to be refined into a more E-like worldview later (e.g. changing the code to use edb configs rather than text files), but I can imagine not many people would feel comfortable with this. The problem is, if we rewrite the code independently it will probably end up looking very similar anyway (stucturally). If anyone has any feelings on this, I'd appreciate it if they let me know before I get into coding. Thanks, Daniel -- "No, the fact that it's in an infinite loop doesn't mean it doesn't work - it just entered a state with which I was previously unfamiliar." http://people.pwf.cam.ac.uk/dh286/publickey.asc .:. keyid 885b170d I am the echo of a distant snowflake; I am the third shadow on the wall.
pgp00000.pgp
Description: PGP signature
