DataSource.cacheAllData questions

Smart GWT Technical Q&A
1

Hi,

I have a few questions about the cacheAllData mode of the DataSources.

  1. When having the full dataset cached, are requests for the images stored in imageFile fields still sent to the server? (I guess they are, since caching those should be configured by sending specific HTTP response headers, which the server side does not do automatically, for now.)

  2. When I have custom fetch operations defined (in the DS XML) besides the default one, how do these behave? Are they sent to the server, or are they cached, too? (The later can be impossible to do properly, because it can involve custom server logic.) Is there a way to configure which fetch operationId-s to cache, and which to let through?

  3. When I have the data cached, there is no need to do a server call to get the results; they are available instantly. Is there a way to get responses to fetch requests synchronously, instead of the usual async API? One year ago, here you have mentioned some preliminary, unsupported, undocumented support for something like this, in the context of actual server calls; since we have everything locally in this case, this should be simplier than that.

Thank you for your help:

Csillag
2

  1. it looks like right now it would attempt to use the cache, which is wrong, so we’ll fix it right away

  2. the default fetch operation is used and results will be returned regardless of operationId. You probably should not attempt to use this feature with multiple operationIds (there’s lots of ambiguity with what should happen in this case).

  3. we don’t have immediate plans to do this at the DataSource layer. Between the requirements implied by #2 and this requirement for synchronized access, you probably want to use a ResultSet to manage your cache instead.

3

OK, so ResultSet it is.

Thank you for explaining.