Prevent store to mark records as saved on empty (0 byte) server response

[Andro00]

What about the _unpredictable_ cases where the server returns an empty response, cero byte I mean? How can I prevent a store to mark records as saved after calling sync() and receiving an empty but non error response from the server? The only solution I can imagine but have not tested it yet, is to hook into global Ext.Ajax and try somehow to stop the event chain that ends up with the store thinking everything is OK and marking records as saved, synced. What would be the best approach?
Thanks a lot for your time.

[bjdurham85]

Hi--,

Is it throwing a non-200 response and/or just 0 bytes?

Bryan

[Andro00]

Hi Bryan, nope, it is a 200, non error response with 0 bytes!

[bjdurham85]

I can't quite tell from your initial post how you've defined the store/events. Do you have (or can you put together) a Fiddle demonstrating your specific scenario so I can take a look?

**Also, does the 0 bytes from your server indicate an error and/or does it normally return a result (A correct/empty response would be useful in your Fiddle)?

Bryan

[Andro00]

Thanks for your time Bryan. Mine is a fundamentals question, then I thought there was no need to post code. You can test this case targeting in your app a properly hosted php script for instance, which produces no output. Then you will see what I mean. The cero byte response mostly happens due to programmer mistakes in server side code, then its unpredictable. But I think Ext should complain about those responses and of course, don't eat that "bad apple". Even when you specify successProperty and totalProperty, which of course are never present in a cero byte response, the records are marked as saved, synced.
Thanks again.

[richardvd]

It is the default behaviour of Ext.data.reader.Reader to interpret an empty HTTP 200 response as successful. The value of the private nullResultSet config determines what will be returned upon a falsy response (null|undefined|empty string).

Add this to your reader config to get the opposite behaviour:

​nullResultSet: Ext.create('Ext.data.ResultSet', {
    total  : 0,
    count  : 0,
    records: [],
    success: false 
})