> From: Oleg Kobchenko > > > From: Raul Miller <[email protected]> > > > > > On Mon, Nov 30, 2009 at 5:21 PM, Oleg Kobchenko wrote: > > > An alternative is to use static client HTML and JavaScript > > > which request one sentence at a time and builds the > > > transcript HTML on the client. > > > > Also: > > > > 1. This would result in different behavior when > > the session is bookmarked. > > > > 2. This would be different from the current (J601) > > session manager where we manipulate the > > entire session state. > > No, the intent of the proposal is exactly the same behavior > of the client and the server, with only two exceptions: > > - HTML is generated at the client > > - unless the whole page is explicitly refreshed (as in > reopening the page including bookmark), each command > execution results in transfer of only this command's result > and not the whole session transcript. >
I can see advantages to this approach. A disadvantage to generating HTML at the client is that various J utilities will need to be ported to Javascript (e.g. parsing for Syntax Highlighting) so they can run client side. Couldn't the HTML generation still happen on the server, but only be for the current command and its result? Or by HTML generated at the client do you just mean that the integration of the existing page HTML & the new content HTML happens on the client? ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
