Re: 'Pure' client-side javscript database?

Jim Davis wrote:
> Richard Cornford wrote:
<snip>
>> (The group's stated "context of use" assumption (as stated
>> in the FAQ); that we are discussing a public Internet use,
>> applies here as the OP mentioned no other context.)
<snip>
> ... . In any case the FAQ does not limit conversation to
> public internet use and while the original poster may not
> have required this for non-public use it definately does
> have potential in that arena.

The FAQ does not limit the discussion to one application context, but it
is not practical to answer questions in a way appropriate for all
application contexts (as there are too many, and a response appropriate
for any one is likely inappropriate (even inadvisable) form many
others). In the absence of information on the context in which a
question is asked it is necessary for respondents to make assumptions
about the context. If all respondents make their own different
assumptions the result is likely to be chaotic, and of little overall
use to a questioner who has a single context in mind (potentially even
harmful).

To avoid this problem the FAQ states the default assumption for the
group, and asks that individuals for whom that default assumption does
not apply state their context (thus avoiding the need for any additional
assumption on the subject). The default assumption (that the context of
use is the general public Internet) has been chosen because it is the
context in which the majority of questions for the group are asked. So
it is the assumption that is most likely to be correct, and saves the
largest number of people form having to explicitly state the context of
their question.

This situation is clearly, publicly stated in the FAQ, and so it is
inappropriate to assume that any other context applies without an
alternative context being explicitly stated beforehand. Any other
behaviour would require that everyone state the context in which they
were using javascript, and so needlessly waste a great deal of
everyone's time. I.E. The default assumption, and the recognition/use of
the default assumption, saves the most time and effort for the largest
possible number of individuals.

Suggestions for realistic alternative strategies are welcome, but seem
improbable.

<snip>
>> But is the browser a client if there is no server?
>
> Yes - or at the very least it may be. The point is simply
> that the client may download an application from a server
> and run it locally. The browser is still a client of that
> server, but the APPLICATION may or may not be.
<snip>

Your definition of "no server" appears to involve slightly more servers
than mine does.

Richard.
Received on Tue Oct 18 03:15:07 2005