Yeah, WDDX is verbose, but so is generic XML --- but their objectives
are:
--- define the structure of complex or simple data.
--- provide a container for the data
--- be human-readable as well as machine readable
WDDX & generic XML meet these objectives,
It is my experience that they are about a wash as far as verbosity
overhead.
Dick
On Mar 26, 2004, at 8:09 AM, Raymond Camden wrote:
> > I made two attempt to use WDDX in my life and the two times
> > it was a lamentable failure.
> > Recently, I discoverd the problem that <CFWDDX will lower
> > case the variable names in a JS structure, which is
> > catastrophic since _javascript_ is case sensitive.
> > I managed to get a result using exclusively lower case
> > variables names, but now I see that the record wont fit in a
> > memo field in Access because it is larger than 64 k! 64k for
> > just a couple of tables containing a couple of variables,
> > cmon, WDDX is much too verbose...
>
> Come on now - is it really fair to blame WDDX because of a limitation
> in
> Access? As it stands - according to Google, the 64k limit only exists
> when
> using Access directly. Via SQL, you should have 1 gig of space.
>
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- Using CFC to dynamically populate a select using javascr... Craig Earls
- Re: Using CFC to dynamically populate a select usin... Claude Schneegans
- RE: Using CFC to dynamically populate a select ... Raymond Camden
- Dick Applebaum