Customer Portal

Get Involved. Join the Conversation.

Topic

    Nisar
    /ci/AjaxCustom/someFunction vs /cc/AjaxCustom/someFunctionAnswered
    Topic posted January 19, 2018 by NisarBronze Crown: 15,000+ Points, last edited January 19, 2018 
    88 Views, 1 Comment
    Title:
    /ci/AjaxCustom/someFunction vs /cc/AjaxCustom/someFunction
    Content:

    When making Ajax calls, I noticed that we can use both "/cc/" as well as "/ci/" (which is used for standard/non-editable files) as the endpoint for the "AjaxCustom" custom controller. In either case, there doesn't seem to be any difference in the response received from the call.

    Are there any differences/advantages of using one over the other? Is "AjaxCustom" a special type of custom controller?

    Version:
    CP3

    Best Comment

    David Ritchie

    Hi Nisar,

    I haven't found any special advantages between the two except that if you just want a quick method to do something without a lot of set up I can just put it in /ci/AjaxCustom without any boilerplate required.  But if I want to do something that is a bigger process which naturally breaks down into smaller classes or more complicated processing I would write my own controller in /cc/.

    Hope that helps,

     

    Dave

     

    Comment

     

    • David Ritchie

      Hi Nisar,

      I haven't found any special advantages between the two except that if you just want a quick method to do something without a lot of set up I can just put it in /ci/AjaxCustom without any boilerplate required.  But if I want to do something that is a bigger process which naturally breaks down into smaller classes or more complicated processing I would write my own controller in /cc/.

      Hope that helps,

       

      Dave