> No, what I meant is that you will actually have URIs like
> "my-scheme:something" around? Or is that still being decided?
Ah ok sorry. I was thinking about that initially, but I decided that
there are going to be more of these once I have the object model sorted,
so the schemes may end colliding. I did feel it wasn't particularly
elegant as well. So it will just be whatever the standard nsIChannels
support (http:/ftp:/file: etc).
> Ah, hmm... Let me think on that.
Cool thanks. For me the question is if I go with a generic storage
connector for each access "protocol", how to handle read and writes.
Calling Connector.Write( nsIStreamListener ); Might work but then each
connector needs to serialise in/out the data.
The best concept I have thus far is similar to the new
mozIStorageValueArray, an quad array of values.
A quad because each value needs to represent an RDF Triple, plus the
value changing (if any). I haven't found a way to ref a unique RDF arc
without the entire triple (one for Axel I guess) so:
RDF S/P/O: message.id, message.subject, "subject", "new subject"
Cheers Boris,
N
Boris Zbarsky wrote:
Neil Stansbury wrote:
Oh ok, I couldn't find a SOAP method that gave me access to those
interfaces. I'll look again.
There might well not be one....
I'm still trying to understand your setup. You're implementing a
protocol handler, right?
Yep an XML message/rpc protocol, using (usually) HTTP as a transport.
No, what I meant is that you will actually have URIs like
"my-scheme:something" around? Or is that still being decided?
I don't want to have to implement multiple Message.Delete() methods
for each underlying XML format. I wanted to transfer a generic request
of Delete() to the "channel" for that connection, and then have it
handle the "Delete()" specifics for that connection type.
Ah, hmm... Let me think on that.
-Boris
_______________________________________________
Mozilla-netlib mailing list
Mozilla-netlib@mozilla.org
http://mail.mozilla.org/listinfo/mozilla-netlib
