RE: CAP Example READ-1

["Mark Poepping" <poepping@xxxxxxx>]

> I have never been convinced that IMAP is an ideal protocol to
> model any protocol after.

I didn't say we should 'emulate', only that we should be willing
to hear and perhaps learn from their experience in these matters.

> > yes, you need to name result sets, deal with garbage collection,
> > and add new error codes (that result set no longer exists since
> > the server restarted between requests).  This is a non-trivial
> > addition, and one that might be beyond the scope of rev1..  If
> > you have a configurable bound for the result set (or items in the
> > set), and allow for (non-)retrieval of specific components, then
> > 'virtual scrollbars' might easily be added as an extension capability.
> 
> By 'virtual scrollbar' do you mean SQL CURSOR type of thing?

yup.

> > I'm also concerned about 'naming' objects (queries, contexts, or
> > whatever) on the server side, will someone clarify or propose the
> > idea for scoping rules on the server side?
> 
> Not documented - but the idea we discussed seems to mean keep
> them in the same session. For a QUERY it just saves some bandwidth,
> especially if we use SQL CURSORS's (a previous post).
> 
> > I thought I heard global naming for the queries (you can't 
> define a query
> > using the same name that I already used), and I didn't hear a 
> plan for the
> > persistence of the names (how long do you keep named queries 
> lying around)..
> 
> I think that was a question. I don't think we resolved it.
> I would vote for session only.
> 
> -Doug

Thanks for the clarification, single session seems manageable.