Support forums » Products » Cute Chat and Cute Web Messeng... » Re: Scalability and decoupled deployment question

Scalability and decoupled deployment question

Last post 10-14-2010, 2:27 PM by lbarcenas. 4 replies.
Sort Posts: Previous Next

  •  10-11-2010, 12:25 PM 64397

    Scalability and decoupled deployment question

    Reply Quote
    Hi,
     
    I am evaluating the chat and messenger install for a potentially high volume load to the chat/messenger application. One thing that I am curious about is the constant calls to the handler ChatAjax.ashx. I believe this is how the application gets refreshed. My questions are :
     
    1. Can I deploy this handler to a different web server and make the chat client script call this?
     
    2.  How much development effort we would need to make this happen?
     
     
    Thanks. 

  •  10-12-2010, 10:03 PM 64413 in reply to 64397

    Re: Scalability and decoupled deployment question

    Reply Quote
    Hi lbarcenas,
     
    Maybe you can explain your requirement on detail. So we can show your the steps to achieve it.
     
    Keep me posted.
     
    Regards,
     
    Ken

  •  10-13-2010, 1:55 PM 64424 in reply to 64413

    Re: Scalability and decoupled deployment question

    Reply Quote
    The chat refresh is run every second and the target URL is the main server. So if my application is in http://myapplication.com/ the refresh URL is invoked from http://myapplication.com/CuteSoft_Client/CuteChat/ChatAjax.ashx.
    What I want to happen is that I want to offload the ChatAjax.ashx requests to some other location so it will not directly interfere with the performance of the main server. I want to be able to set it such that the ajax calls  goes to http://chatserver.com/CuteSoft_Client/CuteChat/ChatAjax.ashx.
     
    From my initial inspection, right now it appears that it needs to be coupled with the deployed application.
     
     I hope this helps.
     
     
    Thank you.
     

  •  10-13-2010, 8:23 PM 64425 in reply to 64424

    Re: Scalability and decoupled deployment question

    Reply Quote
    Hi lbarcenas,
     
    Try deploy two applications, mail server is your site, child server is the chat application.
     
    main server http://myapplication.com/
     
    chat server   http://chat.myapplication.com/
     
    Regards,
     
    ken
     
     

  •  10-14-2010, 2:27 PM 64435 in reply to 64425

    Re: Scalability and decoupled deployment question

    Reply Quote
    Hi Ken,
     
    I tried this but was not able to make it work. The Main server needs to use the user control from the Cute Chat. I also changed the __cc_urlbase variable in LoadSettings.aspx and IntegrationUtility.js.aspx pages to refer to the chat server but did not work either.
     
    Are you suggesting that I use an iFrame inside the Main server to refer to the actual client server?
     
     
    Thanks.
     
     
     
View as RSS news feed in XML