This is the mail archive of the
mailing list for the Guile project.
- To: guile at sourceware dot cygnus dot com
- Subject: gumm ideas
- From: thi <ttn at revel dot glug dot org>
- Date: Thu, 8 Jun 2000 16:12:25 -0700
- Reply-to: ttn at glug dot org
ok, another lazy bastard trudges forward...
@item GUMM is a service. Many hosts can provide GUMM.
Besides archive, some other services are qualification and history.
Qualification involves examining directory trees for standards conformance and
superficial characterization of the source. All extracted info becomes part
of the package history. History information can be shared by sites or ignored completely.
Adopt two hierarchies. Write elisp to modify `define-module' forms. Hook in
a constraint solver to validate a hierarchy. Hook everything into `load'.
Better idea: adopt a single hierarchy, go until someone yells.
Each channel maps to some combination of underlying transport protocols.
Channels are client-prioritized. Look into gnutella.
@item Encrypt Everything
Perhaps a lesson in stupidity? Hope not. Would like to find opinions
surrounding this topic.
@item UI: Use IRC.
Get to survey and play w/ guile IRC clients!
This kind of integration application should be very light. Hopefully wc -l on
the source is less than 500. Imported packages don't count, of course.