[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Re: dbus patch
From: |
Richard Scott |
Subject: |
Re: [Duplicity-talk] Re: dbus patch |
Date: |
Thu, 6 Nov 2008 12:10:08 -0000 (UTC) |
User-agent: |
SquirrelMail/1.5.1 |
Hi,
> Parsing output meant for humans is
> problematic; a frontend needs machine-parsable output.
Would something as simple as outputting information in XML resolve this one?
This could easily be parsed by a computer and contain any number of messages,
formats, languages
etc etc. We could have an --xml-output option to activate?
You could pipe this XML output into a helper application for your front end
that could then talk
to your desktop application via dbus.
i.e. duplicity [options] | desktop-dbus-helper
It seems to make more sense to me to keep things separate, no?
It would also keep duplicity small yet also allow this desktop GUI application
to monitor more
than one duplicity server as you could pipe this output off the embedded server
via SSH to a
central monitoring desktop system? :-)
Rich.
- Re: [Duplicity-talk] Re: dbus patch, Richard Scott, 2008/11/04
- Re: [Duplicity-talk] Re: dbus patch, Michael Terry, 2008/11/05
- Re: [Duplicity-talk] Re: dbus patch,
Richard Scott <=
- Re: [Duplicity-talk] Re: dbus patch, Dan Muresan, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, Richard Scott, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, edgar . soldin, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, Michael Terry, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, Kenneth Loafman, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, edgar . soldin, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, Michael Terry, 2008/11/06
- Re: [Duplicity-talk] Re: dbus patch, edgar . soldin, 2008/11/07
- Re: [Duplicity-talk] Re: dbus patch, intrigeri, 2008/11/07
- Re: [Duplicity-talk] Re: dbus patch, edgar . soldin, 2008/11/06