[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: suggestions

> How does this sound?

I need a cup of coffee :-). Let me try to understand
this visually. (BTW, this email is pretty long perhaps
quite unnecessarily. I just needed to write all this down
to understand this thing myself.)

The initial scenario

              RDF description (URI)

                  RDF Parser

     Application 1           Application 2
  (implements Tellable)  (implements Tellable)

This model would work with the interface we had. Now
you would like to introduce additional layer DataSource

            RDF description (URI)

               RDF Parser

               DataSource

       Application 1          Application 2
   (implements Tellable)  (implements Tellable)

Now the RDF Parser would be aware of objects that implement
the DataSource interface and signal the Tellable objects
about each started and finished DataSource? Sounds complicated
to me.

Your time example did not yet convince me since I believe
the application can notice it has a pending call for a URI
which it is about to call again. It might make more sense
to wait for the previous fetch to finish and then re-initiate
the fetch?

Somehow all this maps down to SAX or SAR (Simple API to RDF
documents) where there are two methods startDocument() end
endDocument() which do about the same thing but only for one
application. We have already extended this concept to support
multiple receivers. If you come up with one more use-case then
I might buy the idea.. :-)

Would it help if the end (URI) return call for a Tellable
object included the object reference to the parser who did
the parsing?

Tellable t1, t2;

SiRPAC s1,s2;

s1.register (t1);
s1.register (t2);
s2.register (t1);
s2.register (t2);

s1.fetch (URI1);
s2.fetch (URI2);

-> would result in calls

t1.start (URI1, s1);
t1.start (URI2, s2);
t2.start (URI1, s1);
t2.start (URI2, s2);
...
etc.

Here, I can see there needs to be something more abstract than
SiRPAC so we could call is DataStore, yes, which would involve
two methods register() and unregister()? Did I come down to
the right conclusion?

Janne
--
Janne Saarela           | Visiting scientist
Email: jsaarela@w3.org  | World Wide Web Consortium http://www.w3.org/