If the set of params is growing (i.e. changing on you) it's worth simply making the input a struct.
mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ On 17 February 2010 09:20, Wil Genovese <jugg...@visi.com> wrote: > > I am writing a web service for the company I work at and I have a question > at to how to handle a very large number of input parameters. > > The basic web service is this. A client will send us the search params for > data they want to search and we return a result set. My question is we have > around 115 (and growing) different search criteria items that can be passed > into to run a search. How would you handle that? > > Named Value List in a single parameter? > ordered CSV in a single parameter? > some sort of data structure in a single parameter? > 115+ single params? Ugh - I know there has to be a better way than this. > > Thanks, > > > Wil Genovese > > One man with courage makes a majority. > -Andrew Jackson > > A fine is a tax for doing wrong. A tax is a fine for doing well. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:330803 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
