Re: wish: could composite store info about datastores that have been changed?

Axel,

I got my own HTTP server working and have been able to test more easily.
And I can update Web files now with HTTP PUT upload. I will do some more 
testing and cleaning and then make a new preliminary package. I hope ftp 
will work too with minor corrections but I still need to test that.

I agree with you that having a RDF server is often better and we are 
using servers too. Mainly for annotations but we have done experiments 
with bookmarks as well. However, after having done that I strongly think 
it is good to also have simple interfaces for normal people who may not 
have access to RDF servers right away. And being able to update RDF web 
files gives me just that. So, please don't throw that away.

 > All our interfaces are deprecated without replacement. They're not as
 > good as they should be, and the separation between reading and writing
 > is one of the things we have on our queue. Tentatively, this is not
 > really decided upon yet.

I separated reading, writing, and updating by using several composites, 
but they mainly help keep track of the files with some of my own 
tracking. I'll try to do my own wrappings around them as packages when I 
have time.

I have not seen anywhere that RDF interfaces are deprecated. If they are 
it is not clearly communicated to interface users. E.g. if I look from 
xulplanet there is nothing:

http://www.xulplanet.com/references/xpcomref/xpcomref1.0/nsIRDFCompositeDataSource.html

And the same is true in many other places. Maybe this info could be 
offered more readily?

Thanks for your help Axel!

Marja