On Tuesday 09 August 2005 18:32, Dawson, Michael wrote:
We are currently working on a small project to test AJAX feasibility for
us. We found that it is a great deal of work compared to simple page
I've got a simple wrapper JS function that goes around the Sarissa crosbrowser
xmlHttpRequest,
On Monday 08 August 2005 23:34, Marlon Moyer wrote:
ability to use flash, html, ajax,etc. I was thinking about creating
all of the business logic as a set of web services. Any thoughts,
Pitfall- web services are slow to execute, certainly much slower than an Ajax
post/get.
--
Tom
On Monday 08 August 2005 23:34, Marlon Moyer wrote:
ability to use flash, html, ajax,etc. I was thinking
about creating
all of the business logic as a set of web services. Any
thoughts,
Pitfall- web services are slow to execute, certainly much
slower than an Ajax
post/get.
I thought
On Tuesday 09 August 2005 15:49, S. Isaac Dealey wrote:
I thought AJAX apps generally used webservices to fetch their data...
isn't that the reason they use the XmlHttpRequest object? (and the
reason why X ended up in the acronym).
In the context of having to submit a form, run the webservice
On Tuesday 09 August 2005 15:49, S. Isaac Dealey wrote:
I thought AJAX apps generally used webservices to fetch
their data...
isn't that the reason they use the XmlHttpRequest object?
(and the
reason why X ended up in the acronym).
In the context of having to submit a form, run the
I rarely use web services, instead preferring to just use GET and POST
operations. The XmlHttpRequest object was designed for fetching
remote XML, but it's really nothing more than an HttpRequest object,
and can be used as such. There's some XML-related stuff, but at the
core is just simple
an XML packet to the AJAX request. Simple and very effective.
M!ke
-Original Message-
From: S. Isaac Dealey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 09, 2005 9:50 AM
To: CF-Talk
Subject: Re: Architecture thoughts
On Monday 08 August 2005 23:34, Marlon Moyer wrote:
ability to use
Have to second this one. Just like Flash, building DHTML/JS Remoting
apps is a lot of work. If you've got a large HTML-based UI already,
however, there are often places where some simple remoting calls can
make a HUGE difference in percieved performance and user friendliness.
As an example, a
I'm tossing around ideas for the architecture for a new project. I'd
like to keep the interface flexible, meaning I'd like to have the
ability to use flash, html, ajax,etc. I was thinking about creating
all of the business logic as a set of web services. Any thoughts,
pitfalls that I should
Implement your application as a set of CFCs that your UI's connect to.
For HTML, they'll hit them directly. For Flash and JS Remoting,
you'll use some facade CFCs. The application CFCs would be
instantiated via Application.cf(m|c), so they're always present, no
matter what type of connection is
10 matches
Mail list logo
