[1.0] Logic behind blanket renaming of Ajax... to Direct...

  1. #1

    [1.0] Logic behind blanket renaming of Ajax... to Direct...

    Among many good things that are coming with the forth-coming 1.0 release, one thing that caught me by surprise was the blanket renaming of Ajax prefix in the toolkit to Direct.

    I really could not understand the logic behind this one. As a web developer, the term "Ajax" comes naturally to me. And it sounding logical everywhere it was used in the toolkit (AjaxEventArgs, AjaxMethod etc.). The term Direct gives no idea and is not a term you associate to web development.

    Can someone from the core team please take time out to give a bit of detail as to why such blanket renaming was necessary??
  2. #2

    RE: [1.0] Logic behind blanket renaming of Ajax... to Direct...

    i believe the rename is to align with ExtJS's Ext.Direct framework

    http://www.extjs.com/products/extjs/direct.php




  3. #3

    RE: [1.0] Logic behind blanket renaming of Ajax... to Direct...

    Okay, I am beginning to see it now!!!
  4. #4

    RE: [1.0] Logic behind blanket renaming of Ajax... to Direct...

    Hi Rahul,

    Yes, the "Ajax" related items were renamed to "Direct" in order to bring them inline with the new Ext.Direct classes (http://www.extjs.com/products/extjs/direct.php).


    The default Direct functionality still performs an Ajax request for client-server communication, although is more feature rich and in the future will also include options for configuring client-server communication without limiting the language to just "Ajax".


    The "Long Polling Provider" will provide a Comet based implementation which opens a direct communication channel for messages to be passed between the client-to-server and server-to-client.


    In the past "push" communication was a similar concept. Comet communication will simplify building scenarios such as "chat" or real time data updates such as stock quotes or just any scenario where you don't want to be constantly polling the server on a timed event.


    Think of "Direct" as enabling the next level of client-server communication without being limited to just "Ajax".


    Hope this helps explains the rational for the change. Feedback always appreciated.


    Geoffrey McGill
    Founder
  5. #5

    RE: [1.0] Logic behind blanket renaming of Ajax... to Direct...

    Hi Geoff, Thanx for taking time out to reply. Does that mean the reverse-Ajax that I requested in a previous Feature Request thread is there in Ext 1.0??
  6. #6

    RE: [1.0] Logic behind blanket renaming of Ajax... to Direct...

    r_honey (1/6/2010)Hi Geoff, Thanx for taking time out to reply. Does that mean the reverse-Ajax that I requested in a previous Feature Request thread is there in Ext 1.0??
    Not with the v1.0 release, but we do hope to have something available this year. We're still in the research phase.


    Geoffrey McGill
    Founder

Similar Threads

  1. [CLOSED] How to control ajax request (direct method)
    By bakardi in forum 1.x Legacy Premium Help
    Replies: 1
    Last Post: Mar 07, 2012, 1:33 PM
  2. [CLOSED] embed display logic in ext container
    By T3rryChan in forum 1.x Legacy Premium Help
    Replies: 1
    Last Post: Aug 24, 2011, 3:40 PM
  3. Execute Ajax/Direct Event from Client-Side?
    By Tbaseflug in forum 1.x Help
    Replies: 5
    Last Post: Dec 16, 2010, 5:35 PM
  4. Gridpanel - Force Save - then Ajax/Direct event?
    By Tbaseflug in forum 1.x Help
    Replies: 1
    Last Post: Nov 24, 2010, 11:04 AM
  5. Renaming <Content> to <Body>
    By geoffrey.mcgill in forum Open Discussions
    Replies: 6
    Last Post: Oct 19, 2009, 4:31 PM

Posting Permissions