Re: [Fresco-devel] Graphic_var's and server stability

Neil Pilgrim wrote:

> For some reason I thought of the tutorial as an architectural
> introduction, but of course its a programming one too :) BTW, we'll need
> an update as and when resolve_server is used wrt the nameserver not
> being mandatory, etc. Maybe it might be worth having somewhere to list
> extra parts to the tutorial that need adding, like this? A task perhaps?
> (we could use the wiki, but a task gives more of a way to say when we're
> completed, which would be useful IMO)

well, I doubt certain tasks will ever complete, so having a task in
the issue tracker for them wouldn't help a lot. I prefer the idea
of a wiki page as a sandbox for additions. But of course, the tutorial
itself (the online version) can be annotated to collect comments,
enhancement requests, etc. That's not optimal, since there is (right
now) no way to track what version these comments were related to, and
thus when they get obsolete. But anyways, it's a start...

> TBH something like this is maybe more important than just an appendix:
> to introduce people to programming in fresco, we need to teach them
> corba first, without putting them off too much. Then again, people
> should read *all* the docs ;)

I don't think teaching corba is our scope. It's really more of
a summary of the techniques to be used (in particular the stuff that
isn't part of corba itself, such as distributed ref counting).

But we should point out where to find good material to get familiar
with CORBA.

Regards,
		Stefan