Confirmed users, Bureaucrats and Sysops emeriti
2,976
edits
RDF:Interfaces: Difference between revisions
Jump to navigation
Jump to search
we decided not to be threadsafe
(→rdfIDataSource: link tests) |
(we decided not to be threadsafe) |
||
| Line 1: | Line 1: | ||
To prevent namespace conflicts with the existing interfaces, these new interfaces use the rdfI* prefix, instead of nsI* They use interCaps naming, so that there is no confusion in JS between the old and new interfaces. They also use the subject/predicate/object terminology contained in the RDF specification, instead of source/property/target. | To prevent namespace conflicts with the existing interfaces, these new interfaces use the rdfI* prefix, instead of nsI* They use interCaps naming, so that there is no confusion in JS between the old and new interfaces. They also use the subject/predicate/object terminology contained in the RDF specification, instead of source/property/target. | ||
The RDF node and service implementations are thread | The RDF node and service implementations are only available on the main (UI) thread. | ||
The enumeration methods are replaced almost entirely with visitors. A visitor uses synchronous callbacks to return results in a "snapshot" without expensive intermediate storage allocations. | The enumeration methods are replaced almost entirely with visitors. A visitor uses synchronous callbacks to return results in a "snapshot" without expensive intermediate storage allocations. | ||