Re: CGI vs Tk for application backend

Concerning web applications, I dislike the fact that you have to complete reload your page for the tiniest change. By chance I found CGI::Ajax at CPAN which makes it easier to use XMLHttp. disadvantage: it produces and uses a lot of JavaScript/DHTML.

Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"

Comment on Re: CGI vs Tk for application backend

Replies are listed 'Best First'.
Re^2: CGI vs Tk for application backend by pg (Canon) on Oct 01, 2005 at 16:21 UTC
"I dislike the fact that you have to complete reload your page for the tiniest change." 100% agree, and technologies like XML island (DHTML category) etc is aimed to address this issue. At this point, it seems like javaScript/DHTML is the most common way if you wish to address this. Add a little bit for people who is not familiar with DHTML: it is not another standard similar to HTML or XHTML, but rather a very vague concept to group any technology that make web page "dynamic".	[reply]

Replies are listed 'Best First'.

Re^2: CGI vs Tk for application backend
by pg (Canon) on Oct 01, 2005 at 16:21 UTC

"I dislike the fact that you have to complete reload your page for the tiniest change."

100% agree, and technologies like XML island (DHTML category) etc is aimed to address this issue. At this point, it seems like javaScript/DHTML is the most common way if you wish to address this.

Add a little bit for people who is not familiar with DHTML: it is not another standard similar to HTML or XHTML, but rather a very vague concept to group any technology that make web page "dynamic".

[reply]