Has there been any progress on this issue? I'm working with a customer that likes the Web interface I wrote for my personal use (<URL:http://www.netspace.org/users/dwb/lwgate/>, but real-time interaction seems to be a requirement which I cannot deliver. I need to be able to have a Web server process LISTSERV commands and then immediately send the user the results of those commands (not just a page, "command accepted, you will receive email to confirm that it was successful"). Is there a Web administration interface for LISTSERV? If not, is there a real-time query/response interface which could be used by an application I write myself? If not, is there a specification of the LISTSERV mailing list file formats, and dare I build an application that would edit them directly? What about linking LISTSERV records with a SQL database? I've been extremely pleased with LISTSERV for many years, but it seems that ListProc may provide the interface (ILP) I need to meet these deliverables and the soon-to-be-released looks like a completely off-the-shelf solution. David On Tue, 9 May 1995, Eric Thomas said: >>(6) Simple gopher and WWW interfaces to list archives. > >We are working on a state of the art WWW interface for LISTSERV. Here is >an (edited) excerpt from an internal design document: > >Functional overview >------------------- > >The interface will provide the following functionality: > >1. Access to list archives: an interface in the style of the VM gopher > interface at SEARN, with a search function (system dependent). > >2. Online LISTSERV documentation: user's and list owner's guides will be > available through the web. > >3. Search/display list of lists, list of servers, etc: basic functions > allowing the user to look for a list matching certain search patterns, > to display a list of servers (built from *PEERS.NAMES), etc. Requires > backbone status. For servers subscribed to the LISTS database updates, > the full list description will be available with point and click ease. > >4. Subscriber assistance for local lists: users can browse information > about the lists hosted on the local server, and subscribe, set their > options, etc. This uses the X-CONFIRM protocol to prevent spoofing. > >5. Subscriber assistance for all lists: users within the licensed domain > can use the server to help them manage their LISTSERV subscriptions > with point and click ease. This is basically #3 with the server > keeping track of who is subscribed to what list (local or global), and > the necessary authentication. >6. List owner assistance for local lists: the list configuration is > displayed in a GUI fashion. The list owner can modify all sorts of > things by clicking around, and finally update the list. > >To answer the obvious question, there will be some serious authentication >but I do not want to discuss this in public. I am not in a position to >give a release date either because we have not explored all the question >marks. But we are definitely working on WWW support. ---------------------------------------------------------------- David W. Baker Associate Systems Developer [log in to unmask] BBN Planet, Business Solutions