Available... to a Web service?  They are available to Live sessions
(Ensemble/Flex apps).

You could always assert the inferred triples and store them.  TDB is a
good choice for this kind of approach.

-- Scott

On Nov 9, 9:53 am, Joseph Shea <[email protected]> wrote:
> Hmm....is there any way to modify queries or anything that can be done
> to a SM script to make these inferred triples available?
>
> On Nov 9, 10:43 am, Scott Henninger <[email protected]>
> wrote:
>
> > Joe; TopBraid Live uses session to hold data in memory.  You can see
> > the emulation of this when using Ensemble with localhost (TBL Personal
> > Server).  A file will appear in TBC-ME holding session data.  You can
> > inspect this file to see that data being held in the session.  The
> > same data structure will be use in Live with remote access.
>
> > Therefore as long as you session is active, you will only need to run
> > your SPIN inferences once.  Also, if you log into the server from
> > different machines using the same id/pwd, the session data will be
> > available all machines.
>
> > Web services is different as the RESTful service and therefore server
> > state is not guaranteed to be retained.
>
> > -- Scott
>
> > On Nov 9, 7:40 am, Joseph Shea <[email protected]> wrote:
>
> > > Hello all. I am interested on how inferred triples act on a server in
> > > an in memory model. For instance, if I trigger SPIN to run on the
> > > server startup, will I have access to those triples forever (until the
> > > server is restarted), or if I would have to run SPIN rules every time
> > > I need to access them.- Hide quoted text -
>
> > - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to