>So you agree that serializing a page instance while the request is
still being processed
... is probably a bad idea, yes. Try it out the other way :P.
Sven
On 09/24/2013 01:49 PM, Tobias Gierke wrote:
So you agree that serializing a page instance while the request is
still being processed
So you agree that serializing a page instance while the request is still
being processed (my current approach) is likely the cause of the
glitches I'm seeing with some (put not all) of the pages , right ?
>> hook into DefaultPageStore#**storePageData()
> custom IPageStore will be needed
Th
>> hook into DefaultPageStore#**storePageData()
> custom IPageStore will be needed
That's what I meant.
Sven
On 09/24/2013 01:15 PM, Martin Grigorov wrote:
On Tue, Sep 24, 2013 at 12:51 PM, Sven Meier wrote:
You could just mark the page to be "bookmarked" (e.g. via MetaData on the
RequestC
On Tue, Sep 24, 2013 at 12:51 PM, Sven Meier wrote:
> You could just mark the page to be "bookmarked" (e.g. via MetaData on the
> RequestCycle) and hook into DefaultPageStore#**storePageData() to store
> the page alongside in the database.
I don't think this will help much.
The page can be requ
You could just mark the page to be "bookmarked" (e.g. via MetaData on
the RequestCycle) and hook into DefaultPageStore#storePageData() to
store the page alongside in the database.
Sven
On 09/24/2013 12:06 PM, Tobias Gierke wrote:
Hi,
I'm currently investigating a bug in our application that
Hi,
I'm currently investigating a bug in our application that is most likely
caused by the very "brute-force" way I implemented a generic in-app
bookmarking feature.
The basic requirement is something along the lines of "Users should be
able to create an (internal) bookmark for virtually any
