[RDF] Encapsulating resources with the context

[Jonas Liljegren]

Wraf stores the resource objects in a cache in order to save time and
memory.  The object holds the custom method jumptable and the
information about all types and properties.

But the list of methods, types and properties will be diffrent
depending on which interfaces are used.  It's up to each agent to
declare the scope of the discussion by declaring what interfaces to
use.  This means that we cache one resource object (for a specific
uri) for each combinatin of connected interfaces. (The order of
connection specifies the chain of authority.)  -- This is how the
current CVS version works.


The assumption here is that only a few combinations will be used, so
that the same cache can be used by most of the sessions.  Changes of
what interface used will eventually be confined to updated versions of
the core interfaces.


> Every resource object lives in the context of their retrieval.  The
> original object is the service object, which is unique for each
> session.  A session consist of the 'discussion' between the Service
> and the Agent.

This would require unique objects for each session and even for each
retrieval within the session.  As a compromise, I will encapsulate the
cached objects with a context wrapper.  The context will hold pointers
to the caller, the filters and the session.

-- 
/ Jonas  -  http://jonas.liljegren.org/myself/en/index.html