> The design I have in my head right now is to write the engine in C and
 
 >the UI strictly in HTML and JavaScript.  If done right, we can keep   
 >most (all?) of the HTML out of the server engine, and also avoid the   
 >need for a template engine.   
  
 these days, it seems the state of the art is to keep HTML mostly static and
perform rendering in JavaScript. So yes. 
  
 I'd still ditch the C, and build a stateless variant of the port-504 protocol
hosted in citserver itself. That would be enough to break the depedency on
having an "engine" per se in webcit, which is necessary because webcit is
currently acting as a TCP concentrator for port 504. 
  
 That's a big part of what it takes to make webcit horizontally scalable.

 

Reply via email to