Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8149093
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T14:46:46+00:00 2026-06-06T14:46:46+00:00

The normal JSON approach looks something like this: { list: [ { header1: some

  • 0

The normal JSON approach looks something like this:

{
  "list": [
    {
      "header1": "some value",
      "header2": "some other value"
    },
    {
      "header1": "some value",
      "header2": "some other value"
    },
    {
      "header1": "some value",
      "header2": "some other value"
    },
    ...
  ]
}

But when I use this, there is a major overhead, because of all the “header1” and “header2” stuff.

So I thought about a more CSV like approach:

{
  "headers": [ "header1", "header2" ],
  "list": [
    [ "some value", "some other value" ],
    [ "some value", "some other value" ],
    [ "some value", "some other value" ],
    ...
  ]
}

but the ExtJS4 stores are more fond of the first style. Is there an easy possibility to use the second format or should I convert it on the client?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T14:46:47+00:00Added an answer on June 6, 2026 at 2:46 pm

    You should be using Ext.data.Store with an array reader and ajax proxy. You do not need any headers on the server side, you should just define what your headers are going to be in the model on the client side. So for an example, you could use code like this on the client side:

    Ext.define("MyModel", {
        extend: "Ext.data.Model",
        fields: [
            {name: "header1"},
            {name: "header2"}
        ]
    });
    var theProxy = new Ext.data.proxy.Ajax({
        timeout: 120000,
        method:  "POST",
        url:     "your_url_here",
            reader:  new Ext.data.reader.Array({
                root:          "list"
            })
    });
    var store = new Ext.data.Store({
        proxy:      theProxy,
        model:      "MyModel"
    });
    

    Make sure when you define the model that the fields are in the same order as the array returned from the server.
    And this would be what is returned by the server:

    {
      "list": [
        [ "some value", "some other value" ],
        [ "some value", "some other value" ],
        [ "some value", "some other value" ],
        ...
      ]
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have loaded data to normal list view from JSON array like this JSONArray
A normal UserControl looks like this in XAML: <UserControl x:Class=mynamespace.foo ...namespaces...> <!-- content -->
Is it normal or hopefully best practice to use package.json in my project even
Normaly a ajax Datasource (for Datatables) looks like this: aaData: [ [ Trident, Internet
I use this code to retrieve JSON details from php call and I add
i want to analyse the json just like: [{id:ssq,name:双色球,term:2010092,date:2010-08-12 19:15,numbers:{normal:3,13,19,27,28,30,special:2},jackpot:30000000},{id:3d,name:3D,term:2010216,date:2010-08-12 19:55,numbers:{normal:6,8,8},jackpot:-},{id:qlc,name:七乐彩,term:2010093,date:2010-08-11 20:45,numbers:{normal:08,09,10,11,16,21,27,special:26},jackpot:0},{id:dfljy,name:东方6+1,term:2010093,date:2010-08-14 18:30,numbers:{normal:4,1,3,9,7,2,special:羊},jackpot:12866531},{id:swxw,name:15选5,term:2010217,date:2010-08-12 18:45,numbers:{normal:1,3,5,13,15},jackpot:5693612},{id:ssl,name:时时乐,term:20100811-23,date:2010-08-12
I can retrieve data from normal json link But I have one link which
A normal form of what I am trying is this. MyClassFacadeLocal cls = new
Generating normal columnar data in excel file is quite easy but does any one
I have a simple ajax call like this: $.ajax({ url: u, type: POST, dataType:

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.