Quantcast

Wicket ajax page versioning

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Wicket ajax page versioning

Nazaret Kazarian
Hi,

I would like to ask whether wicket keeps version of pages when changes
are made with ajax requests.

If it does, it seems as a waste of resources, unless ajax back button
support is implemented (with javascript history, etc).

Thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Wicket ajax page versioning

Adam Gray
That's funny, I was just really hoping for a way to do the exact opposite
so that the back button works correctly.

On Wed, Dec 7, 2011 at 7:31 AM, Nazaret Kazarian <[hidden email]
> wrote:

> Hi,
>
> I would like to ask whether wicket keeps version of pages when changes
> are made with ajax requests.
>
> If it does, it seems as a waste of resources, unless ajax back button
> support is implemented (with javascript history, etc).
>
> Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Wicket ajax page versioning

Nazaret Kazarian
Well, as far as I know, since Wicket does not yet support browser back
button with ajax (only some experimental extensions exist), keeping
track of the history does not make any sense right?


2011/12/7 Adam Gray <[hidden email]>:

> That's funny, I was just really hoping for a way to do the exact opposite
> so that the back button works correctly.
>
> On Wed, Dec 7, 2011 at 7:31 AM, Nazaret Kazarian <[hidden email]
>> wrote:
>
>> Hi,
>>
>> I would like to ask whether wicket keeps version of pages when changes
>> are made with ajax requests.
>>
>> If it does, it seems as a waste of resources, unless ajax back button
>> support is implemented (with javascript history, etc).
>>
>> Thanks.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Wicket ajax page versioning

Igor Vaynberg-2
In reply to this post by Nazaret Kazarian
no. we do not keep versions for ajax requests. we will, when the back
button is supported.

-igor

On Wed, Dec 7, 2011 at 4:31 AM, Nazaret Kazarian
<[hidden email]> wrote:

> Hi,
>
> I would like to ask whether wicket keeps version of pages when changes
> are made with ajax requests.
>
> If it does, it seems as a waste of resources, unless ajax back button
> support is implemented (with javascript history, etc).
>
> Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Wicket ajax page versioning

Nazaret Kazarian
Thanks Igor for confirming.




2011/12/7 Igor Vaynberg <[hidden email]>:

> no. we do not keep versions for ajax requests. we will, when the back
> button is supported.
>
> -igor
>
> On Wed, Dec 7, 2011 at 4:31 AM, Nazaret Kazarian
> <[hidden email]> wrote:
>> Hi,
>>
>> I would like to ask whether wicket keeps version of pages when changes
>> are made with ajax requests.
>>
>> If it does, it seems as a waste of resources, unless ajax back button
>> support is implemented (with javascript history, etc).
>>
>> Thanks.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...