I would love to be able to use the Query-of-Queries to query any collection (List, Array, File, ...). A new feature in .NET 3.5 is LINQ that allows SQL like querying of most any collection. Or maybe similar to how LogParser works which lets you use SQL like querying on files.

To include Spry as the AJAX built in

That actually makes a lot of sense. One of the items on my list was tighter Flex integration but I was not sure about the right questions to ask. Thanks!

1. support for nulls

2. ability to instantiation cfcs from in-memory variables (iow, don't make me write to disk only to turn around and do create object from that concrete file)

3. built-in ORM capabilities, preferably Hibernate under the hood

4. flatten="true' attribute on cfpdfform when action="populate" and using the destination attribute

5. low on the list, but total cfscript support so I could, if I wanted to, write entirely in cfscript (I go back and forth on this but having the option would be nice)

6. support for creating a jar-like construct with cfcs

I'll stop there for now. ;-)

@Matt - Great suggestions! I really like the idea of jar-like constructs for cfcs..Thanks!

Now that we're all using cfqueryparam in every query, it would be nice if the cfsqltype attribute didn't require the "cf_sql_" at the beginning of every value and save our fingers some typing.

Supporting multiple-page Tiff from cfimage

That last comment reminded me of 2 more ideas:

CFPodCast -- a CF tag that will dynamically make a Flex SWF streaming MP3 "widget" on the client. Not a Flex widget -- I want to be able to customize it on the server (preload it with specific MP3s, change the colors, security settings, whatever) *before* it hits the client.

...and in regards to the cfvideo tag mentioned above, I'd love a "video" version of the cfPodCast tag I just described. Can we build a dynamic flex based streaming video "UI widget"? and have it start as CF code so various options can be controlled by the server first? (i.e. pre-load it with specific videos, etc).

thanks.

1. File upload progress control (with multi-file support)

2. charts..add funnel & pyramid types

3. More control over "automagically" inserted cf code, i.e for cfform, bundle js in tidy externals.

4. Built in support for dealing with undeliverable mail in the domino administrator.

5. Alerts for specific log events, generate an email /sms etc..

6. quicker support for latest version of os x.

7. support for full search friendly / simple URL's. e.g
/page.cfm?id=1 becomes /page/id/1

8. built in unit testing

9. Adobe to show more support for Open Source community developed projects

10. kill or upgrade the exchange area of the adobe website its not very useful.

11. add ability to send email via MS exchange tags (it will only become truly useful when this happens)

Off the top of my head:
1) Allow us to specify case insensitivity with query of queries
2) Full support for inline structures
3) namespacing like cfimport prefixing at the application / server level so we could define cf tag libraries similar to java
4) Better return format support on cfc method calls (IE: automatically convert my results to whatever format the client requests and allow xml as one) This is a great feature that just needs to be filled out better.
5) Viewable examples in the CF documentation
6) Update support for tags like cfmail so they can handle secure connections
7) Give us user management for cfadmin in standard
8) E4X type xml support (makes dealing with XML a breeze)

I'd like them to extend the shorthand array/struct creation to allow nesting, so you could do:

<cfset config = [
   { first:'John', last:'Doe' },
   { first:'Paul', last:'White' }
] />

Oh, awesome, hadn't seen that!

Mail queue throttle control. For example, if my app dumps 10,000 messages into the mail spool, it'd be great to have a setting - either in the server or in the cfmail tag - that told the server how many to pass off at X intervals to the smtp servers - i.e., send a max of 50 messages every 30 seconds until the spool is empty.

Even better would be the ability to re-order the queue so that only xx number of messages to a certain domain (aka yahoo.com) per spool parsing would be sent.

@David Ryan: FWIW, flash forms are no longer 'stripped down' in CF 8. All keyword restrictions, etc have been removed. It should be said though (and anyone, feel free to correct me because I'm probably a bit off on this), that flash forms were built on Flex 1.5(?) which was a *server* product that compiled the SWF on the server. Flex >2 compiles the SWF locally which is then deployed to the server. So we're talking about 2 totally different things here. So it's really not that easy to just 'upgrade' flash forms to a higher version of Flex. I'm curious though, as to why so many people want CF/Flex solutions. MXML is really not all that difficult to use/learn. What is the motivation for some of you? Cost? Dynamic code? Just curious...

a short list:
- nested transactions (by name)
- handling empty elements in list functions (turn on/off)
- new CFARGUMENT attributes: CALLBY="reference|value", list="Yes|No" and "max, min, pattern" from CFPARAM
- CFCSV, CFGPS, CFCRAWLER, CFDOC, CFXLS, CFSKYPE/CFMESSENGER, CFCLUSTER, CFSOUND/CFCHAT/CFVOIP/CFTALK, CFVIDEO/CFTV, CFJSR170, CFAMF
- compare(arg1, arg2) for structs, arrays and even queries results in: 0=equal, 1=not equal, -1=arg2 extends arg1, having more keys/rows
- replace(string, sub, sub2 [, scope [, start [, end] ] ]) == scope:   LAST / REST; start:   default value is 1; end:   -1 = len(string)
- find(sub, string [, start [, end [, scope] ] ] == start:   default value is 1; end:   -1 = len(string); scope:   FIRST / LAST
- cluster features: clear memory caches for all, cfsharefile so file is in short time available on all servers
- A function to get current settings of certain tags; rule: if you can set something there must be a function to get information about it; examples: cfschedule jobs, cftransaction isolation level, CFSETTING enablecfoutputonly/showdebugoutput, CFERROR template...
- see below: useTag(), execTag()
- see below: tag defaults

especially I second the mentioned:
- Query-of-Queries to query any collection
- Named arguments in scoped functions, so I can make use of the super scope in cfc


== useTag(), execTag() ==

useTag(tag="cfqueryparam", innerCode="", attributecollection="#structX#", text="")
tt = useTag(tag='cfquery', attributecollection={name="qData", datasource=dsn},
   innerCode = 'SELECT fieldlist
               FROM tablename
               WHERE columnanme LIKE #useTag(tag="cfqueryparam", attributecollection={value=searchstr, cfsqltype="CF_SQL_VARCHAR"} )#
            ');
execTag(tt);

This would make anything usable in CFSCRIPT and in EVALUATE()
and there is no need to make functions out of any tag in CF9.

useTag(tag="cfloop", attributecollection={from="1", to="10", index="iii"} innerCode=useTag(tag="cfset", text="t = iii") )



== tag defaults ==

Setting default attributes for tags (usually placed in 'Application.cfc') so you don't have to write always all attributes again and again.
<cftagdefault tag="cffile" action="READ">
   <cfsettagdefault name="charset" value="iso-8859-1">
</cfdefault>

<cftagdefault tag="cffile" action="WRITE">
   <cfsettagdefault name="mode" value="644">
</cfdefault>

<cftagdefault tag="cfquery">
   <cfsettagdefault name="datasource" value="mydb">
</cfdefault>

<cftagdefault tag="cfhttp">
   <cfsettagdefault name="proxyserver" value="127.0.0.1">
   <cfsettagdefault name="proxyPort" value="9999">
</cfdefault>

example:
<cffile action="READ" usedefaults="yes" ...>

I would see a new tag <cfssh user="" pass="" server="">some linux / unix commands to run</cfssh>. At the moment i have to use ssh = createObject("java","com.trilead.ssh2.Connection").init("localhost"); to do this job.

MASSIVE IMPROVEMENTS IN CFDOCUMENT.
Seriously - strange support on CSS, that may or may not get overwritten, different CSS support in the Header and Footer sections, Header and Footer scaling against the Margin size. "bugs" as in needing extra documentation just to figure out what it's trying to, and what it's successfully doing in the render engine. Upgrade it to the most recent version of itext.

Better support for storing a massive amount of objects in an array. If I use any of the existing ORM frameworks to return an array of objects, the performance takes a nose dive.

The ability to create accessible content while still using the AJAX and EXTJS tags.

i.e. When using cfgrid - CF could generate the table as HTML then add the EXTJS grid functionality rather than creating the grid all via JS code.

[...]resource[...]

* JEE server deployment option with standart edition.

CFTHROWCOLLECTION

This should be wrapped around multiple cfthrow tags and only when the last cfthrow is processed in that block, the process would abort and return an array collection of exceptions via “cfcatch.COLLECTION” variable to be handled in whatever way the developer sees fit.

<cfthrowcollection>
   <cfif Not FirstName>
      <cfthrow… />
   </cfif>

   <cfif Not LastName>
      <cfthrow… />
   </cfif>
</cfthrowcollection>

In many cases you want to be able to collect more than one exception at a time, especially when building service oriented components that need to validate certain incoming calls. Normally you would have to build a custom error collection mechanism and return the results back to the requestor via the request scope. I find this ungainly at times. I think this could be handled better via cfthrow which can return standard or custom error type messages that could then be parsed out fairly elegantly and sent to the client UI (Flex, Ajax, HTML) for friendlier error displaying.
Let’s say I had a series of checks on first and last name in my PersonService and these failed at any time, then the following would be triggered, collected and finally returned as a collection.

<cfthrow type=”ContactManager.Person.FirstName” message=”The First Name is required.” />
<cfthrow type=”ContactManager.Person.LastName” message=”The Last Name is required.” />

On the caller side inside my cftry and cfcatch tags I can parse out the messages base on type and return them to the client all at once or in whatever manner I wish. I think this would be a powerful and very useful extension of the cfthrow’s capabilities. The cfthrow as it is only allows the first occurrence to run, but with the help of a “cfthrowcollection” tag, I believe it will simply extend its usefulness and overall ability.

This one is simple but I am surprised how often I need it.

An enhancement to Trim (and LTrim, RTrim) to take a character to trim off the ends as opposed to the current trim than only trims spaces. Ideally one could supply a character or list of characters to trim (the default would be spaces as it is currently).

The character(s) to trim would be the second argument so not to effect current usage.

Say you had a string with a few extra characters:

cfset sResult = Trim("<mytag>","<,>") -> returns "mytag"

The extended trim functions would work, as trim currently does, and only effect the end points of the string. So:

cfset sResult = Trim("<my<>ta>g>","<,>") -> returns "my<>ta>g"

and:

cfset sResult = Trim("<<<<mytag>>>>>>>","<,>") -> returns "mytag"

(We could also see RETrim function!)
cheers

David

Full and reliable support for dbvarname in CFPROCPARAM.

One major frustration is that when a CFLock times out... we don't get any information about the lock holder - the victim gets the exception, but is left guessing as to who is being greedy with the lock...

========

Allow better control over memory usage with queries. If I need to loop over every record in a huge recordset (and don't need random-access and don't need to back up)... let me say that up front so CF doesn't try to keep more than one record (or 'blocksize' records) in memory.

=========

Improved whitespace control. Even with whitespace control enabled in the CF administrator... too much junk whitespace still goes out. At least eliminate lines that contain nothing but whitespace.. and perhaps provide a CFSetting with some more options (like... trim every line)

=========

Any chance we can get some more useful timings in the CF debug information? It can get very difficult to parse out where the performance problem is when each module's timings aren't adjusted for the timings of the modules they call..

=========

Improve type detection to allow integer parameters to be passed to Java methods without JavaCast() - it seems more than a little silly that numbers (especially obvious integer values) are treated as Double and CF doesn't even look for 'int' in the method signatures...

=========

Provide an option to suppress (or complain about) SQL comments in CFQuery (i.e. throw a 'bad SQL' exception if the query contains an un-quoted comment). This would go a long way toward prevention of SQL injection attacks... along with...

Provide an option to suppress (or complain about) multiple SQL expressions (or, more exactly, un-quoted semicolons) in a CFQuery

Neither of these would be a complete substitute for diligent use of CFQueryParam, but there are cases where CFQueryParam isn't the answer - like if you want the 'order by' clause to be controlled from a form. You could write something like:

SELECT #Form.ColumnList#
FROM {tableName}
WHERE {conditions}
ORDER BY #Form.SortBy#

CFQueryParam helps in the 'WHERE' clause (and in 'VALUES' and 'SET' clauses for insert and update queries), but it doesn't help elsewhere.

Eliminating semicolons and SQL comments from the toolbox probably wouldn't eliminate SQL injection risks completely, but it would make the job more difficult...

=========

Some improvements in variable scoping could go a long way...

1) provide control (via a CFSetting, perhaps?) over which scopes get examined when resolving an unscoped variable name. Users could then tell CF that all un-scoped references are ONLY in 'variables' scope, saving the monsterous verbosity of putting 'variables.' on everything.

2) provide a [PASCAL-like] 'with' construct to temporarily push a scope onto the front of the list of searched scopes (similar to what CFLoop does with a query object).

3) provide a single 'input' scope containing the merger of 'form' and 'url' scopes.

4) provide an option to automatically 'var' all new variables in functions...

4a) remove the requirement to 'var' everything at the top of a function...

5) provide an option to *REQUIRE* that all variables are declared (via 'var' or some other construct)

===

And a few other things for those of us who aren't just returning stuff to browsers...

Provide a way to catch or disable CFLocation.

Provide a way to catch CFAbort.

I would like to see vspidering done through the CF admin rather than physically logging on to each server and running the vspider locally from the cmd line. I'm speaking of a webfarm or clustered environment of course. Don't know if it's possible but would be time-saving and a nice feature.

@Dan Did you manage to pass on your list? Looks like it may have been quite large...