Comments on Template Language Document So this seems a very impressive piece of work which is a good approach to templates. I have a few questions/comments/requests. 1) We should make certain the process works by trying it on one of reasonably complex cases. Perhaps you have already done this? I have little doubt it will work but some issues could come up when we try it out. I have an ulterior motive to ask this. Namely with an example, I can get a student working here on conversion issues. Also we need an example for legal people who want to patent "TangoWisdom" 2) My next two questions are "cosmic". It would be useful to see if your powerful capability could be helpful in other cases such as interfacing Tango to Lotus Notes. This is investigating general assertion -- XML is the natural Web interface language for Tango to talk to server based applications. Do you have any thoughts here. Again we could get somebody at NPAC to look into this but I would like into in terms of your overall insight. 3) I wonder how fast this process will be as it seems there could be quite a bit of overhead if several requests. So I thought it would be useful if Servlet cached its results. In WebWisdomNT we have a scenario that strongly favors caching. One is processing more or less simultaneously one request from master and N identical ones from each client. Can the servlet recognize this? One would not need to keep a very deep cache as "memory" is only needed for the course of a Tango transaction (a few seconds). This is very different from trade-off in normal servers (where one gets for average US proxy servers only a 50% cache hit) and suggests that a simple memory based cache would be sufficient. Is in fact servlet multi-threaded so each client gets a separate instance? If we continue these thoughts, there is the simple caching of full pages that I discussed above but also caching of the XML objects (as fetched from database) as one would re-use most such objects from page to page. There is a company (Persistence Software) which is in Java Server and object ? relational database mapping business. Their "corporate crown jewel" (or one of them) is the ability to cache at the middle tier object level after one has converted from relational database to object view. Persistence licensed JavaBlend technology to Sun. 4) From the sublime to the mundane. I think you misunderstood my rather uninspired comments about databases and XML. I am not advocating replacement of a database by XML flat files. I am just noting that XML is a useful way of exporting databases to flat files and so convenient for short lists which could be in a database but perhaps sufficient in a file for simple cases. The user information in Tango(2 room) is an example of such data where I remember you were to store configuration in a flat file. I think we agree here? 5) I wondered if you were putting wwwalias in the WebWisdomNT database. I do need this! 6) Is template an argument to servlet call. I recommend this as it enables support of customizable frontends where each client can choose their display. This allows people on lousy lines to choose the low bandwidth view or blind people to choose "sonified" page. This "universal access" concept is a hot topic here!