From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <8ccc8ba40705211037j6607cd8o4c805e43ac45a0b2@mail.gmail.com> Date: Mon, 21 May 2007 19:37:20 +0200 From: "Francisco J Ballesteros" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] XML In-Reply-To: <4651D685.5090905@conducive.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <13426df10705210957w2982fa31lc6c22ff554fcd629@mail.gmail.com> <1179767515.8323.193.camel@linux.site> <4651D685.5090905@conducive.org> Topicbox-Message-UUID: 6c808bf2-ead2-11e9-9d60-3106f5b1d025 > > Do you remember XML being helpful on any particular occasion? I'm really > > curious. In omero, I've found recently a place where using XML to convey the UI tree from the UI server to the viewer would win (perhaps) wrt using a file tree. this particular case is when the link between the omero server and the UI viewer has a really bad latency. In this case, the current viewer scans the tree (one level at a time) to see changes and update the UI. Even when notified of subtrees that changes, it still has to read the root of the subtree (one RPC), do the same for inner panels (another), and so and so and so. However, we're still experimenting with this and I think that just placing a "toc" file in the root of the tree (with the equivalent of du -a) would permit the viewer doing its work in just two RPCs. Of course, using a real fs instead of xml lets us use all the fs tools, as you all know, that's why we don't actually use xml. But since you asked, I have to say that that's the only place I've seriously considered using xml (or similar) to replace a file tree. Perhaps others have more cases where xml could be helpful.