Socket Tutorial Guidelines [was: thank you notes]

[Dar Scott]

On Monday, November 25, 2002, at 03:50 PM, Richard Gaskin wrote:

> If there's a need for interoperability between Rev-based apps from 
> different
> authors, we could define a standard for the function name, something 
> like
> SocketDictionary().

I think it is a good idea to start thinking about this.

Six not-very-concrete thoughts off the top of my head:

Some method of one scheme should be very easy for newbies to use.

The basis should allow for RPC, messaging, state reflection and maybe 
other models.

The overall model should allow client-server, source-sink as well as 
other relationships.

Models should be very Revolution and optimized about Revolution concepts 
such as handlers, functions, strings, properties, objects...

Standards are OK where they help, but not when they get in the way.

This should be tough/robust/tenacious rather than reporting lots of 
errors.  (But maybe there can be two ways to do this.)

Dar Scott