can't assert into remote http: datasource

NEW
Unassigned

Status

P3
normal
19 years ago
7 months ago

People

(Reporter: myk, Unassigned)

Tracking

Trunk
Future
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
nsIRDFDataSource.Assert() fails on a remote datasource loaded via http:.  For
example, the following code returns "false":

myDataSource.Assert(myResource, myProperty, myValue, true);
itWorked = myDataSource.HasAssertion(myResource, myProperty, myValue, true);
alert(itWorked);

If the datasource is loaded via a file: URL, however, the code returns "true".

Build Date & Platform Bug Found: 2000-10-07-06 Linux

Comment 1

19 years ago
Yep, this isn't supported yet.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
(Reporter)

Comment 2

19 years ago
Is this perhaps a very small fix that has been bundled together with the
implementing of flush() for http: datasources so the modified RDF can be POSTed
back to an HTTP server?  There are situations where it's useful to be able to
modify some remote RDF without needing to save changes, so if it's just a matter
of enabling Assert() for these kinds of datasources, and it hasn't been enabled
because flush() wasn't working, don't wait for flush().

Comment 3

18 years ago
*** Bug 71855 has been marked as a duplicate of this bug. ***

Comment 4

16 years ago
Isn't this a prohibitive problem for people who consider to use Mozilla/XUL to
make a fronted for a client-server database?

Comment 5

16 years ago
s/fronted/frontend/ in my last comment (#4) -- by frontend I mean forms with
read/write access to live data on the server.

Updated

16 years ago
QA Contact: tever → nobody

Comment 6

15 years ago
IMHO, http datasources should only take assertions if they're writing them back
to the server.
Datasources are unique, so modifying the mozilla mirror of it introduces side
effects which are not reflected in other clients running on the same ds.
One can think of those side effects both as bug or as feature. If two windows
access the same datasource, do they want the original content or do they wanna
sneak information from one context to the other?
I personally like to think of it as bug.

Does anyone know of a xml-rpc or soap schema to implement remote rdf?

Comment 7

15 years ago
waterson left the building
Assignee: waterson → nobody
Status: ASSIGNED → NEW
QA Contact: nobody → core.rdf

Updated

7 months ago
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.