\> -----Original Message-----
> From: Micha Schopman [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 16, 2005 11:12 AM
> To: CF-Talk
> Subject: RE: Ajax and CFCs
> 
> The amount of consistency is in the hands of the developer. It just is
> about documenting the format.

You're thinking too small here, Micha.  We're not saying we can't get the
job done - this isn't a "help me get this out the door" issue.  It's a
broader question.

Why should such a fundamental thing as passing structured data be left
completely to individual implementation?  Why should that implementation be
tightly coupled to the solution built?

Why shouldn't my interface be able to switch from obtaining data from CF to
obtaining data from WebSphere without having to rebuild the transport
mechanism on WebSphere?

The complaint (well... my complaint) is that this is such a low level issue.
Passing structured data from a server to a client needs to be solved by
EVERY SINGLE person doing AJAX style applications.  Yet we have hundreds if
not thousands of incompatible solutions.

When you see that doesn't it at least indicate to you that a useful umbrella
standard would be a useful thing?

Again, it's not that it can't be done or that doing a one-off or a personal
standard is difficult.  It's that the situation is screaming for a clear,
widely-adoptable standard.

Jim Davis




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware (www.logware.us): a new and convenient web-based time tracking 
application. Start tracking and documenting hours spent on a project or with a 
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:215232
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to