From: Andreas K. <and...@ac...> - 2006-08-17 20:54:30
|
One of the services I wanted to put into Tcllib, based on the 'safe' comm foundation is the primitive nameserver I did years ago, see http://www.oche.de/~akupries/soft/pool/f_net_ns_server.tcl.html Except when I started the docs/spec for the new implementation I found myself quickly on the road to complexity, because of a number of questions I came up with in need answers ... For now the doc/spec is quite incomplete and actually more a set of notes I started to make to organize my thoughts and get something coherent out of of whatever notions are tumbling through my subconscious. Below is the relevant section of the spec to be. Question is, how far should I go in complexity. What is the most simple yet general use case ? In the worst case I could even do a series of services with different complexities and data models ... Gods, now I have started thinking about pluggability, one API, different databases underneath ... Stop! ... ______________________________________________________________ The simplest database, relationally speaking, would be a table table { name : string id : list (host port) } This leaves the structure and semantics of 'name' to the clients of the service. Not the client objects, but the users of these objects. Is this the application name ? Example: Tkcon The name of a service provided ? Example: log Do we allow multiple ids per name ? I.e. do we want 'name' to be a unique key or not ? What about situation where we have multiple instances of a service or application, but 'name' has to be unique. Registration then either disallows the multiple instances, or the name gets internal structure to distinguish between instances. When we have structure it starts to make sense to make it explicit, i.e. instead of storing a string representation we break it apart and store components explicitly. And now we have begun sliding down the slippery slope of complexity. Actually, before writing the last sentence, a different thought bubbled up out of my subconscious, that I am apparently re-inventing LDAP, where the stored records have complex structure with many keyes, attributes, possibly nesting, and can be searched for by any component. That made me realize that my questions had put me really well on the road to higher complexity. Still. What would we use in the Tcl world as records ? My guess would be nested dictionaries. ______________________________________________________________ -- Andreas Kupries <and...@Ac...> Developer @ http://www.ActiveState.com Tel: +1 778-786-1122 > -----Original Message----- > From: tcl...@li... > [mailto:tcl...@li...]On Behalf Of Andreas > Kupries > Sent: Wednesday, August 16, 2006 9:28 PM > To: Hemang Lavana; Tcllib Devel > Subject: Re: [Tcllib-devel] A proposed new package ... Asking for > comments. > > > > > > Andreas Kupries wrote: > > > > > > > > What is the problem with 'ip' ? > > > > > > > Maybe it's just me: when I see ip I think of internet protocol, > > > intellectual property, etc but never "interp". > > > > I see. I could see the second, forgot the first. > > > > > Just -events is fine with me. > > > > Ok. That it will be. > > The new options -interp and -events have been implemented, and the > testsuite extended as well. Package version is now 4.3.1. > > -- > So long, > Andreas Kupries <aku...@sh...> > <http://www.purl.org/NET/akupries/> > Developer @ <http://www.activestate.com/> > ---------------------------------------------------------------------- > --------- > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Tcllib-devel mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcllib-devel |