> >The object represents a data recordset. The attributes are the data
> columns. There are no addtional attributes in my CFC, only the data column
> names are passed to the attributes scope.

I don't quite see what we're buying ourselves with this CFC.  It's
certainly a good exercise in design and catalyst for some great
discussion, but isn't it sort of reinventing the wheel?

We already have an object (ColdFusion's Query type) that represents a
data recordset and has attributes that are the columns.  Addtionally,
the underlying Java RowSet beneath a CF Query contains the interative
functions that are re-implemented in this CFC.  If you wanted to use
them, why not just use the RowSet to begin with?  I could see this CFC
being handy if it wrapped these already existing methods and was
maintained as a "wrapper" in case those methods changed.

Now, I think the idea of a collection of iterators could be handy. 
It'd be cool to see an ColdFusion iterator "interface" that would act
as a standard way to iterate over queries, arrays, structs, or, well,
anything else.  Maybe we should focus on an interface (probably using
Java as an example) and then work on concrete implementations like
query?

Concerning efficiency, I think any code released to the outside world
as a development tool should employ the most efficient methods known
to the developer writing them.  If it's an internal one-off project, I
can understand letting some stuff go, but to release something that's
a fundamental type like an iterator without having it work as
efficiently as possible probably isn't ideal, regardless of the market
(SOHO, internal, public release).

-- 
For Tabs, Trees, and more, use the jComponents:
http://clearsoftware.net/client/jComponents.cfm

----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]

Reply via email to