Hi Maarten, > - Is it a good idea to include a link to the download sites?
Most definitely. I'd like to complete it a bit more before deciding on actual URLs though. > - Security: perhaps talk about the /restrict refinement and secure-serve? Very good idea. Though maybe I should just link to a more reference manual/user guide type document that could be updated independently. > - What is hard for people is the notion of async programming (that's what I > learnt from working with Graham). Although there is /deferred, nobody (knows > how to) use it. > - A P2P sample? Well up I have to admit I'll need to get it clear in my mind to be able to write about it :) Maybe Graham (hey Graham?!) could point out some topics/difficulties that should be addressed. > > As for the architecture document.... I am currently making some heavy changes > to inner rugby, such as: > > - Adding modules > - A simple task based system in the IO scheduler, which allows you to add > tasks (chunks of Rebol code) to a queue that will be executed if there is no > IO. Very simple threading ;-) > - This will be used by redirect, the function for server chaining. Sounds sophisticated. > Once things have settled down in that coding area I'll produce an > architecture document, with protocol specs as well! Great! > --Maarten > > On Monday 28 January 2002 06:29, you wrote: > > Hi Rugby team, > > > > I've made a start at some Rugby documentation as promised. > > > > Here's my first output (not complete). I'd appreciate comments. > > > > http://www.codeconscious.com/rugby/rugby-doc.html > > > > The source of which is: > > http://www.codeconscious.com/rugby/rugby-doc.txt > > > > Thanks > > Brett. > -- > To unsubscribe from this list, please send an email to > [EMAIL PROTECTED] with "unsubscribe" in the > subject, without the quotes. > -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
