[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: User Resources
From:       Zak Jensen <coolguyzak () gmail ! com>
Date:       2005-08-23 13:08:59
Message-ID: 21bb44f30508230608539cd883 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hmm.. sounds like it could be an interesting application of Tenor/the CLE :D
 When you create a file that should be backed up, the application lets the 
CLE know, and then it stores something like "<meta>backmeup</meta>"

 On 8/23/05, Johan De Messemaeker <johan.demessemaeker@telenet.be> wrote: 
> 
> On Monday 22 August 2005 17:02, Zak Jensen wrote:
> > It is definitely needlessly complex (IMHO) to create a daemon that
> > uses FAM/etc to track everything that changes.
> 
> FAM wasn't needed in my model. The application talks to the daemon 
> whenever a
> file is added/deleted that is worth backing up.
> 
> My example of a daemon is maybe not quite correct. It could be anything
> really. The only functions of the program is to listen to application
> requests that can be:
> 
> 1) program registrations of some kind
> 2) a program that requests locations from files of type X/Y/Z
> 
> That's all there is really: the program stores file locations.
> 
> Regards, Johan
> 
> _______________________________________________
> kde-usability mailing list
> kde-usability@kde.org
> https://mail.kde.org/mailman/listinfo/kde-usability
>

[Attachment #5 (text/html)]

<div>Hmm.. sounds like it could be an interesting application of Tenor/the CLE \
:D</div> <div>&nbsp;</div>
<div>When you create a file that should be backed up, the application lets the CLE \
know, and then it stores something like \
&quot;&lt;meta&gt;backmeup&lt;/meta&gt;&quot;<br><br>&nbsp;</div> <div><span \
class="gmail_quote">On 8/23/05, <b class="gmail_sendername">Johan De Messemaeker</b> \
&lt;<a href="mailto:johan.demessemaeker@telenet.be">johan.demessemaeker@telenet.be</a>&gt; \
wrote:</span> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px \
0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Monday 22 August 2005 17:02, Zak \
Jensen wrote:<br>&gt; It is definitely needlessly complex (IMHO) to create a daemon \
that <br>&gt; uses FAM/etc to track everything that changes.<br><br>FAM wasn't needed \
in my model. The application talks to the daemon whenever a<br>file is added/deleted \
that is worth backing up.<br><br>My example of a daemon is maybe not quite correct. \
It could be anything <br>really. The only functions of the program is to listen to \
application<br>requests that can be:<br><br>1) program registrations of some \
kind<br>2) a program that requests locations from files of type X/Y/Z<br><br>That's \
all there is really: the program stores file locations. <br><br>Regards, \
Johan<br><br>_______________________________________________<br>kde-usability mailing \
list<br><a href="mailto:kde-usability@kde.org">kde-usability@kde.org</a><br><a \
href="https://mail.kde.org/mailman/listinfo/kde-usability"> \
https://mail.kde.org/mailman/listinfo/kde-usability</a><br></blockquote></div><br>



_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


[prev in list] [next in list] [prev in thread] [next in thread]