From: Will Hartung (willh_at_msoft.com)
Date: Wed Apr 28 2004 - 11:44:24 PDT
I have a question for application developers.
What do you think of Soups? Do you like them? Do you hate them? Favorite
feature? Worse Feature?
Is the ability to simply store an arbitrary frame in a soup valuable
compared to having to set up a schema? Are managing "inter soup" aliases a
problem?
At a glance, Soups seems to give a flexible ISAM storage system, without
having to worry about table definitions etc, but not quite making the leap
to being an "OODB", notably when you try and store a Frame graph of items
that may already be stored in a soup (which makes the system simpler). The
closest thing to a schema is the specification of indexes on the soup.
I notice that indexes are typed ('slot 'string), what happens if the slot
value is not the same type as specified in the index, will the index skip
it?
The other uniqe aspect of the Soup is the "union soup" to handle splitting
soups to removable storage.
Any idea why the number of tag's on a soup are limited to, what, ~600?
I'm just curious as someone who has seen them from afar and what folks who
had to manage them thought about them as a storage mechanism. Do you think
in hindsight a mini-SQL like system would have been more flexible and easier
to use?
Thanx for any thoughts you have.
Regards,
Will Hartung
(willh_at_msoft.com)
-- This is the NewtonTalk list - http://www.newtontalk.net/ for all inquiries Official Newton FAQ: http://www.chuma.org/newton/faq/ WikiWikiNewt for all kinds of articles: http://tools.unna.org/wikiwikinewt/
This archive was generated by hypermail 2.1.5 : Thu Apr 29 2004 - 08:30:02 PDT