View source for John Samuel's additional comments

After some reflection and review of the other comments, I thought of    other things to add to the recommendations, or at least to pass on    to Evan.
If int322 is going to continue the work on html5 the        int222/322 (and probably 422) courses will have to be changed in        sequence, with int222 changing a semester or two before int322        does.  If we are going to continue html5 into 322 then we are        changing the paradigm the current 222/322 courses are based on -        client-side only in one course and server-side only in the        other.  This change appears to be a reasonable idea, based on        the exponential adoption rate of html5 and the need for it due        to all the different devices out there, I'm just saying that it        could be a mess if the transition isn't coordinated and planned        carefully, because students are all over the place in which        courses they take when. 
Due to the above, maybe we should have a professional option        course in html5, for those students who have already taken 222        and 322, or will have done so before the changes are        implemented.  Because of the way that students don't all follow        in step (coop, work, etc.) there will still be some  students        around for awhile that don't have any html5 and they'll be at a        disadvantage if they don't get a chance to pick it up.  This        would give cdot more students sooner who are capable of working        on their projects, which is what started this whole thing.
After further thought I think that int322 should definitely        teach php, rather than python.  The paradigm that php teaches        (take the markup language and insert programming language        statements) is more common than the cgi model of perl and python        (output html from within the perl or python code), and also php        is by far the most widely used open source web programming        language these days.  While the suggestion to use python instead        (or as well) was made so that students would learn some of a        scripting language that could be used for non-web programming        (especially in the open source courses and projects), I think        that this is best served by an option course in scripting, which        has been suggested already.
John