Matt Pasiewicz wrote:
> Interesting ... I wonder if that might not also help with scalability
> of large datasets. I wonder if there is some middle ground to be
> found on this front ... not sure if we can get meaningful gains by
> having a mixed clientside/server-side hybrid (and still retain the
> "exhibit experience"), but I can't help but wonder.
There was a project called Backstage, which I started but haven't had
time to continue, that attempts to deal with large datasets by
dynamically constructing an RDF database on a server, loading the data
into it, and then serving the data off as any conventional web app
would. As author of an exhibit, you would manage your html and data in
much the same way, but you just need to link to a Backstage server
rather than (or in addition) to exhibit-api.js. Think of it as "renting
a faceted browsing web app on the fly".
There was a thread on that
http://simile.mit.edu/mail/ReadMsg?&msgId=23836
<http://simile.mit.edu/mail/ReadMsg?&msgId=23836>
but the demo is no longer running. You could still see the html file
http://people.csail.mit.edu/dfhuynh/misc/backstage-demo.html
but the server that it links to is no longer up
http://dfhuynh.csail.mit.edu:8181/backstage/api/backstage-api.js
Note that this still does not address the crawl-ability issue, since the
html still does not contain the data.
David
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SIMILE Widgets" 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/simile-widgets?hl=en
-~----------~----~----~----~------~----~------~--~---
