Changes between Initial Version and Version 6 of Ticket #6073


Ignore:
Timestamp:
Mar 11, 2008, 11:21:38 PM (12 years ago)
Author:
bill
Comment:

Hmm, I thought close() was just supposed to clear information related to the request (ie, the current fetch() call), not clear all cached data. 

//	summary:
//		The close() method is intended for instructing the store to 'close' out 
//		any information associated with a particular request.

Seems dangerous for close() to erase everything that was downloaded from a URL... ComboBox could likely be calling close() on every keystroke, thus every new keystroke would cause an XHR, and it would grind to a halt.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6073

    • Property Cc josh@… added
    • Property Milestone changed from to 1.2

  • Ticket #6073 – Description

    initial v6  
    1 Currently ItemFileReadStore will only fetch once from the server.  This works well in most situations but many times it seems like people want to be able to tell the store to re-fetch data from the server.  Usually the answer is "use QueryReadStore" - sometimes this is not appropriate or even possible (see trac 6071).  Also, relying a a dojox component for your data store might make some people nervous as dojox implies "experimental" (even if QueryReadStore is quite stable).
     1Currently !ItemFileReadStore will only fetch once from the server.  This works well in most situations but many times it seems like people want to be able to tell the store to re-fetch data from the server.  Usually the answer is "use !QueryReadStore" - sometimes this is not appropriate or even possible (see #6071).  Also, relying a a dojox component for your data store might make some people nervous as dojox implies "experimental" (even if !QueryReadStore is quite stable).
    22
    3 From lurking on the forums I see this request periodically and it seems to frustrate a lot of people that this functionality is not possible and usually results in strange hacks, suck as creating a brand new QueryReadStore with the same URL as the original store and assigning it over your existing store.  (e.g. mywidget.store = new_store)
     3From lurking on the forums I see this request periodically and it seems to frustrate a lot of people that this functionality is not possible and usually results in strange hacks, suck as creating a brand new !QueryReadStore with the same URL as the original store and assigning it over your existing store.  (e.g. mywidget.store = new_store)