Prevent enormous nomenclature of items from being printed in each select

> I have enormous nomenclature of items (package types). On my form  
> there is a
> list of goods, each good has a  select, which determines package  
> type. For
> each good's select, entire nomenclature is filled as a list of  
> <option>'s.
> This causes network traffic issues, when transfering form to browser.
> Is there a way to send nomenclature only once to the browser and  
> after that
> to populate selects?
>
> Each time a new good is added, entire nomenclature is sent to the  
> browser in
> XML response.
> Is there a way to avoid repeating sending of the same nomenclature?

> Nikolay,
>
> On Feb 16, 2008, at 8:46 AM, Nikolay Chillev wrote:
>> I have enormous nomenclature of items (package types). On my form
>> there is a
>> list of goods, each good has a  select, which determines package
>> type. For
>> each good's select, entire nomenclature is filled as a list of
>> <option>'s.
>> This causes network traffic issues, when transfering form to browser.
>> Is there a way to send nomenclature only once to the browser and
>> after that
>> to populate selects?
>>
>> Each time a new good is added, entire nomenclature is sent to the
>> browser in
>> XML response.
>> Is there a way to avoid repeating sending of the same nomenclature?
>
> We can't really optimize this when the page first loads, as the idea
> is to send HTML to the client that can initially displayed as-is
> without requiring any JavaScript processing on the client. But we
> could optimize this in Ajax responses. And if this optimization is
> done, then you could leverage it as well to speed up the initial page
> load, as you could sent the page with empty selects, and on
> xforms-ready run an xxforms:script action, which triggers an event,
> which populates the lists.
>
> Do you have a situation right now where you are sending an updated
> itemset during an Ajax request, i.e. after the page is loaded? If you
> do, I am wondering how fast this is.
>