Nick Han wrote:
> I have used both of these APIs in my test environment. I think they
> both work well. There are pros and cons in choosing one over the other,
> and most of these issues I encountered were minor. For instance,
> ajaxCFC is easier to set up, but the thing I don't like about it is the
> passed parameters are transformed and received as array arguments by the
> CFCs. As for CFAJAX it is more work to set up, I like the fact that
> arguments are received by functions the way there have been passed by
> the calling page. So you keep variable naming in tact for
> self-documenting and easy debugging. Also with CFAJAX you can't use it
> within CFC framework. So there's a mixed bag of good and bad between
> the two.
Personally, I've found cfajax fairly easy to deal with once you get it
installed and working, so I don't really consider that an issue.
Although the documentation talks about mappings and such there's really
no need for the mapping.
I haven't tried ajaxCFC but I don't like the sound of what you described
with reference to variables.
You *CAN* use cfajax in a CFC environment if you make some
modifications. For example, you could take the functions out of
functions.cfm and put them into a component, and then do something like
this in your functions.cfm file:
<cfinclude template="/ajax/cfajax.cfm">
<cfset createObject("component","ajaxFunctions")>
<!--- expose the following functions --->
<cfset myFunction1 = ajaxFunctions.myFunction1>
<cfset myFunction2 = ajaxFunctions.myFunction2>
<cfset myFunction3 = ajaxFunctions.myFunction3>
Rick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:234912
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
