There are two ways to do "ajax"

Security Issues

When the XMLHttpRequest object operates within a browser, it adopts the same-domain security policies of typical JavaScript activity (sharing the same "sandbox," as it were). This has some important implications that will impact your application of this feature.

First, on most browsers supporting this functionality, the page that bears scripts accessing the object needs to be retrieved via http: protocol, meaning that you won't be able to test the pages from a local hard disk (file: protocol) without some extra security issues cropping up, especially in Mozilla and IE on Windows. In fact, Mozilla requires that you wrap access to the object inside UniversalBrowserRead security privileges. IE, on the other hand, simply displays an alert to the user that a potentially unsafe activity may be going on and offers a chance to cancel.

Second, the domain of the URL request destination must be the same as the one that serves up the page containing the script. This means, unfortunately, that client-side scripts cannot fetch web service data from other sources, and blend that data into a page. Everything must come from the same domain. Under these circumstances, you don't have to worry about security alerts frightening your users.

Post #245,168 by tuberculosis 2/17/06 3:17:15 PM Reply	There are two ways to do "ajax" XMLHttpRequest or you put a hidden IFrame on the page and set its href (which populates it) then get its contents. "Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein "This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush
Post #245,186 by admin 2/17/06 5:52:08 PM Reply	Yeah, I know that. I was asking why you picked that method. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #245,196 by tuberculosis 2/17/06 6:28:53 PM Reply	Lots of reasons many of them historical. "Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein "This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush
Post #245,197 by admin 2/17/06 6:31:38 PM Reply	Were any of them technical? Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #245,224 by tuberculosis 2/17/06 8:14:11 PM Reply	Yes it is not subject to these limitations Security Issues When the XMLHttpRequest object operates within a browser, it adopts the same-domain security policies of typical JavaScript activity (sharing the same "sandbox," as it were). This has some important implications that will impact your application of this feature. First, on most browsers supporting this functionality, the page that bears scripts accessing the object needs to be retrieved via http: protocol, meaning that you won't be able to test the pages from a local hard disk (file: protocol) without some extra security issues cropping up, especially in Mozilla and IE on Windows. In fact, Mozilla requires that you wrap access to the object inside UniversalBrowserRead security privileges. IE, on the other hand, simply displays an alert to the user that a potentially unsafe activity may be going on and offers a chance to cancel. Second, the domain of the URL request destination must be the same as the one that serves up the page containing the script. This means, unfortunately, that client-side scripts cannot fetch web service data from other sources, and blend that data into a page. Everything must come from the same domain. Under these circumstances, you don't have to worry about security alerts frightening your users. "Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein "This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush
Post #245,225 by admin 2/17/06 8:16:07 PM Reply	Yeah, those don't affect us at all. We're entirely single-host (virtual, of course) based. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."
Post #245,231 by tuberculosis 2/17/06 8:25:05 PM Reply	So I showed you mine what's your's do? (BTW the progress indicator is being redesigned next week) "Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein "This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush
Post #245,239 by admin 2/17/06 9:17:00 PM Reply	Re: So I showed you mine Bond trading tools. One is a market evaluation tool, the other is a specialized trading desk application for a particular type of bond. Realtime information updates coupled with AJAX techniques for displaying and manipulating orders and so forth. Regards, -scott
Post #245,247 by tuberculosis 2/17/06 10:35:02 PM Reply	Is this for a trading house or general consumption? "Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein "This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush
Post #245,249 by admin 2/17/06 10:37:38 PM Reply	Both. At least the evaluation tool is. The other is strictly for traders. Regards, -scott anderson "Welcome to Rivendell, Mr. Anderson..."

Welcome to IWETHEY!