Sounds o.k., but please don't forget to include some 'batch' mode, where commands would be read from a file. It is important, since I believe many people use command line tools in replacement for SQL's DDL. Dawid
>> Summed up, reduce complexity, be a friend to the user and enhance >> flexibility. >> >> BTW, I think the long term goal should be to replace them completely with >> a SiXDML interpreter so that using Xindice would be more like using a >> traditional database. Dare Obasanjo is supposed to be working on an >> implementation. We'll see how this shapes up over time, but for now I >> think we can improve the current tools a lot. KW> I've been thinking of how an improved set of command line tools might KW> function. If you guys agree with this starting point, I'll get started on KW> some framework. KW> I was thinking of a command line similar to MySQL, eliminating the slow VM KW> startup KW> for each command. You would run xindiceadmin and get a prompt (this would KW> be the KW> place to add user authentication in the future): KW> /usr/local/xindice/xindiceadmin Xindice>> KW> From here, I'm thinking you would set the collection that you want to work KW> with: Xindice>>collection /db/test KW> Now the user would be able to execute commands against this collection KW> including XMLObjects KW> without having to specify the context each time. After the current command KW> is executed, the user KW> would be returned to the prompt again with the collection still set to the KW> current working collection. KW> To end, there would be a simple 'quit' command that would clean things up KW> and exit. KW> Does this sound more like what we want to work towards? KW> Kurt KW> _________________________________________________________ KW> Do You Yahoo!? KW> Get your free @yahoo.com address at http://mail.yahoo.com
