http://gregwolejko.com/pure-javascript-html-parser/ Web2.0 evangelist on his way to greatness Wed, 07 Jan 2009 02:41:47 +0000 http://wordpress.org/?v=2.6.1 http://gregwolejko.com/pure-javascript-html-parser/#comment-766 einstein Sat, 06 Sep 2008 23:43:10 +0000 http://gregwolejko.com/?p=8#comment-766 A very interesting idea and I think we can use it before sending to db :) A very interesting idea and I think we can use it before sending to db

]]> http://gregwolejko.com/pure-javascript-html-parser/#comment-31 Processing.js | GregWolejko.com Fri, 09 May 2008 19:47:01 +0000 http://gregwolejko.com/?p=8#comment-31 [...] haven’t been too long since I blogged about recent John Resig’s work on Pure JavaScript HTML Parser and now John did it again and released [...] [...] haven’t been too long since I blogged about recent John Resig’s work on Pure JavaScript HTML Parser and now John did it again and released [...]

]]> http://gregwolejko.com/pure-javascript-html-parser/#comment-23 Greg Mon, 05 May 2008 22:03:12 +0000 http://gregwolejko.com/?p=8#comment-23 @Oskar - you've missed my "for the record" line. I would add parsing of the content on the editor's side, between moving content from online editor like FCK or TinyMCE into a db. This won't slow down viewers experience and will lessen server load. A win-win situation. @Oskar - you’ve missed my “for the record” line.
I would add parsing of the content on the editor’s side, between moving content from online editor like FCK or TinyMCE into a db. This won’t slow down viewers experience and will lessen server load. A win-win situation.

]]> http://gregwolejko.com/pure-javascript-html-parser/#comment-22 Oskar Krawczyk Mon, 05 May 2008 21:53:38 +0000 http://gregwolejko.com/?p=8#comment-22 Server-side overload vs. front-end overload... I think I'd rather add some memory to the server than loosing viewers just because the site is dead slow - which eventually will happen if you're consider parsing loads of content (-: Server-side overload vs. front-end overload… I think I’d rather add some memory to the server than loosing viewers just because the site is dead slow - which eventually will happen if you’re consider parsing loads of content (-:

]]> http://gregwolejko.com/pure-javascript-html-parser/#comment-21 Greg Mon, 05 May 2008 21:47:16 +0000 http://gregwolejko.com/?p=8#comment-21 @Oskar - server-side solution is a natural way to go, but sometimes circumstances point to front end. Lessening server load is my primary concern here. Having a highly overloaded server with content being published by a few dozens of authors all at once was an ideal situation for this kind of front-end parsing. For the record: I am of course thinking about parsing before content is uploaded onto server not after publishing :) @Oskar - server-side solution is a natural way to go, but sometimes circumstances point to front end.
Lessening server load is my primary concern here. Having a highly overloaded server with content being published by a few dozens of authors all at once was an ideal situation for this kind of front-end parsing.
For the record: I am of course thinking about parsing before content is uploaded onto server not after publishing

]]> http://gregwolejko.com/pure-javascript-html-parser/#comment-20 Oskar Krawczyk Mon, 05 May 2008 21:22:10 +0000 http://gregwolejko.com/?p=8#comment-20 I know the pain of dealing with clients and their idea of content-committing (aka. copy'n'paste from Word). Still I'd rather use a server-side solution. I know the pain of dealing with clients and their idea of content-committing (aka. copy’n'paste from Word). Still I’d rather use a server-side solution.

]]>