[Tcllib-devel] Http module, organization of modules

[Andreas K. <and...@Ac...>]

Regarding the latest thread on c.l.t about support for HTTP/1.1
in the http package distributed with tcl.

	I like and endorse the proposal of having a base http package
	distributed	with tcl and an expanded version in tcllib. I always
	wanted to have support for http in tcllib to get a more complete
	set of supported protocols but was also loath to move http.

	That way we get http in tcllib without leaving users of the core
	distribution hanging in the wind.

Anybody else out there agreeing or disagreeing with me ?


My second topic is the internal organization of the tcllib modules
directory. Currently we have a flat directory approach where all
modules are immediate siblings of each other. I begin to believe
that modules is becoming a bit crowded now and that we should try
and organize the modules in a more hierarchical fashion. Examples:

*	The modules md5, sha1, crc all generate a hash
	and could be placed into a directory 'hash'.

*	nntp, pop3, mime (smtp), ftp, ftpd, smtpd
	all deal with networt protocols. A directory for
	them could be 'net', 'inet', 'network', or similar.

Partially we are seeing such aggregation already, albeit done in a
different fashion: One module directroy containing several packages,
either independent (mime), or in hierarchically organized namespaces
(math, textutil).

And yes, the proposed reorg. of the directory structure below 'modules'
might be a precursor to a reorg. of the packages names to make more use
of hierarchical namespaces.

--
	Andreas Kupries <and...@Ac...>
	Developer @ http://www.ActiveState.com