Domain: pathf.com
Stories and comments across the archive that link to pathf.com.
Comments · 15
-
for the ignorant anti-microsoft bloviating:
onhashchange
http://www.pathf.com/blogs/2008/03/ie8-html5-and-a/
msie8 is the first to implement this event. don't know what that is? ajax is the most important technological development in browsers in recent history (invented with microsoft's xmlhttprequest object, btw). however, ajax breaks history and bookmarking (can't go forward/ back, can't bookmark deep into an ajax session)
a way around this has been to hijack the hash part of anchor links, since they stay on the same page, but create a history. initially, this hack didn't work for msie, because msie didn't consider hash changes to be part of the browser's history, invoking valid msie hatred (msie7 fixed that oversight). but now, from the back of the class, msie jumps to the front of the class with onhashchange, becoming the programmer's best friend
currently, there is no way to tell when a browser's anchor hash link changes other than with extremly ugly, resource wasting kludges like putting a "heartbeat" on the web page (every 200 milliseconds, see if the url's hash link has changed... vomit). however, here's a recent history emulator without the odious heartbeat kludge (but no bookmarking functionality):
http://www.zachleat.com/web/2008/08/21/onhashchange-without-setinterval/
but now, msie, with onhashchange, makes ajax programming for history/ bookmarking elegant... for the very first time. there's plenty of reasons to hate microsoft folks, but hate them for actual real technical reasons
want one? ok: there's msie8's bullshit compatibility button. since msie8 tries so hard to be compliant for once, it is faced with backwards compatibility issues for rendering sites that only really work on msie now
http://blogs.msdn.com/ie/archive/2008/08/27/introducing-compatibility-view.aspx
ugggh
so the lesson is: by all means, hate microsoft and msie. but make sure your hate is grounded in reality, not ignorant bias which i see in a lot of comments here
-
Re:zk unimpressive
It is a matter of taste. ZK's demo is much more sexy that eacho2. You can even try its power by writing some codes on-line. Anyway, how happens to echo2? Why comes a fork project, Cooee? Cooee - Branch of Echo2 Project
-
Re:How do you fix it?
http://www.infiltrated.net/docs/modsecips.html step by step... If its your own server... If not have the admin slap on mod_security for you and add the same rules in my previous post on this page... www.infiltrated.net/admin.php go for it... That's how I add content. There are a lot of variables to prevent against injections, etc.
Block Spam injections
Directory traversal attacks SecFilter "\.\./"
XSS attacks
SecFilter "<(.|\n)+>"
SecFilter "<[[:space:]]*script"
SQL injection attacks
SecFilter "delete[[:space:]]+from"
SecFilter "insert[[:space:]]+into"
SecFilter "select.+from"
Too many times there are clueless admins (not you per se). But this also tends to be one of the grips on the Ubuntu Document people flame me for. If *semi* even experienced admins can't lock a machine down... Imagine when Ubuntu on Dell becomes the next hot thing. Flame as much as you'd like facts are facts -
ZK
This is good news, but I would highly suggest anyone looking at a tool such as GWT also look at ZK ( http://www.zkoss.org/ ).
While not technically competitors (GWT is all client side, ZK provides a way to handle AJAX requests automatically on the server side) they fill many of the same niches. There is an informative interview available ( http://blogs.pathf.com/agileajax/2006/06/an_interv iew_wi.html )
If you want to jump straight into the ZK demo, check out http://www.zkoss.org/zkdemo/userguide/ -
Old trick, new buzzword
Ouch. Adding a script tag dynamically is old hat in Ajax. See the DOM Based On-Demand Javascript pattern.
In fact, there are a number of project under way that use dynamic script injection to emulate cross-domain XHR. See http://ajaxian.com/archives/jsonp-json-with-paddin g
But worse yet, the argument that developing web applications with Ajax is hard is a straw man. Imagine you had to design a desktop GUI by twiddling with the screen bits directly or, worse yet, implementing application logic in the graphics controller. Blech!
That's the situation with Ajax and webapps right now: writing code in the wrong places and at the wrong level of abstraction.
If you want to simplify how you write webapps using Ajax, try a server side framework like Echo2 or ZK. These allow you to write webapps much like a desktop GUI while working in only one language context -- Java on the Server side. -
Three Reasons for AJAX's Success
As I see it there are three reasons for AJAX's success:
1. It enables a paradigm shift from developing forms based webapps to component GUI webapps.
2. Developing webapps this way is more efficient and less error prone.
3. Both of the above reasons drive many companies to adopt Ajax into their software and change their business model, to SaaS, for example. -
Three Reasons for AJAX's Success
As I see it there are three reasons for AJAX's success:
1. It enables a paradigm shift from developing forms based webapps to component GUI webapps.
2. Developing webapps this way is more efficient and less error prone.
3. Both of the above reasons drive many companies to adopt Ajax into their software and change their business model, to SaaS, for example. -
Three Reasons for AJAX's Success
As I see it there are three reasons for AJAX's success:
1. It enables a paradigm shift from developing forms based webapps to component GUI webapps.
2. Developing webapps this way is more efficient and less error prone.
3. Both of the above reasons drive many companies to adopt Ajax into their software and change their business model, to SaaS, for example. -
It's the Cognitive Load
You can only hold 7+-2 things in your short term memory at once. This limits your ability to learn and problem solve. Complex environments increase the number of concepts you have to juggle in your brain at once -- the cognitive load -- and make errors go up and productivity go down.
This isn't a problem that is unique to open source, of course, but it isn't one that is focused on a great deal, with the exception of frameworks like Ruby on Rails. -
You forgot Open Laszlo
Open Laszlo is a very slick, open source platform for writing Flash apps. They're also working on producing a DHTML/Ajax target for it -- write once, run with multiple runtimes.
Last, you're already starting to see the melding of Ajax and Flash. -
You forgot Open Laszlo
Open Laszlo is a very slick, open source platform for writing Flash apps. They're also working on producing a DHTML/Ajax target for it -- write once, run with multiple runtimes.
Last, you're already starting to see the melding of Ajax and Flash. -
Try mod_security
Sometimes its not feasible to shut down an application because its vulnerable to spam or sql injection. The Apache mod_security module can provide a stopgap until you can fix the app. Probably a good idea to have it in place in any case.
-
Re:This sounds like
Actually, DWR exposes POJO's on the server via Javascript peers in the client.
GWT, on the other hand, is really two things in one: first, it compiles Java code to Javascript, much like javac converts Java to bytecode; big portions of java.lang and java.util are available to the developer. Second, it allows you to execute and debug your code in a JVM. The idea is that the code in the JVM will behave exactly like the compiled Javascript code in the browser.
I think the point of GWT is that good Java programmers are easy to find whereas good Javascript/CSS/XHTML programmers are hard to find. This way they can write Java and produce Javascript. For more on GWT, see here.
-
Re:Do Some Research
First, can anyone even find the patent application?
Second, I've used Morfik WebOS ApplicationBuilder (did I get the caps right?
;-) for some evaluation POC's and have some familiarity with it. Can't say I'm a big fan of it's kludgy IDE interface. Right click doesn't bring up anything useful so you're making trips to the top menu bar all the time. Hopefully, they'll clean it up soon.It (Morfik) also isn't the sort of thing you'd want to write a little sidebar widget in, which is about all GWT seems to be good for at the moment.
Lastly, for me the choice is really about supportability. If I'm going to buy into a proprietary IDE/Framework, I'm going to pick something by a large, established company. So TibCo GI and GWT are worth considering, Morfik is not.
-
Re:Ajax web framework support
Look. We f***ing get it already. You're a lame shill for NextApp. I don't think I could stand to look at Echo2 again after seeing you comment
My apologies, but "FecesFlingingRhesus" is not on our list of paid shills. My best guess is that he might be a member of the cult.
Best regards
--Tod Liebeck (Director of Shills and Level 6 Cult Leader)
NextApp, Inc.