Marije;
>
> Also a manual that says that also one of the people involved should run an
> ntp
> server so that system clocks within the local LAN (assuming that people
> don't
> always play together while connected to a WAN) can be synched to that would
> be useful. And maybe since not all livecoders are also sysadmins... a quick
> guide as to how to set such a thing up, both as clients and hosts.
>
I agree this would be a good idea. Live audio rarely works well at the same
time that virus scanners and firewalls are running, for example.
>
> As a last note, writing the spec in more detail and explain the idea behind
> the workings of each message, along with a description as to how a client
> would connect, would really help.
> It also allows for a close introspection into the written code, which may
> even
> improve the code itself again :)
> (at least that's what I find, when writing documentation).
>
And not just that; to repeat what we talked about in the chat last night; I
think everybody working from a clear spec can save issues, as compared to
working from a specific implementation. Probably the most clear and amusing
example right now is the whole mess that the browser wars are; little of
that would've happened if designers of pages and browsers would have both
just looked at the W3C specs.
While this may sound very critical I do very much appreciate the work that
people have already put into this and feel it's a good idea. My criticism of
these specifications is just a attempt to help advance this project.
Yours,
Kas.
Received on Sat Mar 21 2009 - 15:22:03 GMT