there is another option.
you can use apache JCS cache or open symphony's OScache for caching all
objects that are required during user interaction.
On 6/9/06, Emilia Ipate <[EMAIL PROTECTED]> wrote:
Hello, all!
Is there a solution besides using session, to send some request parameters
from o
Michael Jouravlev wrote:
On 6/9/06, Samere, Adam J <[EMAIL PROTECTED]> wrote:
Emilia Ipate wrote:
> Is there a solution besides using session, to send some request
> parameters from one request to another?
> I would like to implement something like a shopping cart (a
> functionality which need
On 6/9/06, Samere, Adam J <[EMAIL PROTECTED]> wrote:
Emilia Ipate wrote:
> Is there a solution besides using session, to send some request
> parameters from one request to another?
> I would like to implement something like a shopping cart (a
> functionality which needs about4-5 steps) and I do n
PROTECTED]
Sent: vrijdag 9 juni 2006 16:20
To: Struts Users Mailing List
Subject: Re: best way to send parameters through more requests
Emilia Ipate wrote:
Hello, all!
Is there a solution besides using session, to send some request
parameters from one request to another?
I would like to
Emilia Ipate wrote:
> Al, your solution is good, except for one thing: what do you do if the
> user leaves the application at step2? You will have in DB all the items
> the user checked, but they are no longer necessary
>
1) Not if they come back, in which case they'll be delighted you care
juni 2006 16:20
To: Struts Users Mailing List
Subject: Re: best way to send parameters through more requests
Emilia Ipate wrote:
> Hello, all!
>
> Is there a solution besides using session, to send some request
> parameters from one request to another?
> I would like to impl
Emilia Ipate wrote:
Hello, all!
Is there a solution besides using session, to send some request
parameters from one request to another?
I would like to implement something like a shopping cart (a
functionality which needs about4-5 steps) and I do not want to store
the objects in the session
Emilia Ipate wrote:
> So I cannot just hold these objects in session forever,
Fortunately sessions don't generally _last_ forever.
> that's why I think a session mantaining functionality is
> required:
> 1. have a configuration file that specifies exactly what objects
> can be hold in sess
-
From: Samere, Adam J [mailto:[EMAIL PROTECTED]
Sent: vrijdag 9 juni 2006 15:20
To: Struts Users Mailing List
Subject: RE: best way to send parameters through more requests
The thought here(base64 encode) was to store the data on the client.
This would also be a large effort requiring all POST re
solve
your problem in short run ...
So a good idea to avoid it if you can
Regards
-Original Message-
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: 09 June 2006 14:06
To: Struts Users Mailing List
Subject: Re: best way to send parameters through more requests
Emilia Ipate wrote
. Anything else will most likely cost more in development
effort than upgrading hardware.
Adam
-Original Message-
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: Friday, June 09, 2006 9:06 AM
To: Struts Users Mailing List
Subject: Re: best way to send parameters through more requests
Emilia
Emilia Ipate wrote:
> Now the question comes: when does the object come useless? It is useless
> when users gets to step 5 and also when from a middle step (like 3)
> decides to get out of the this 5 step request-chain. In both cases, the
> object should be removed from session. I would say to have
Subject: RE: best way to send parameters through more requests
Frequent deleting from session is not very good
In a cluster that would mean updating the states of session on so many
servers on the clusteryou can appreciate that this is an overhead
and a great performance hit Request, hidden fields
PROTECTED]
Sent: 09 June 2006 13:27
To: Struts Users Mailing List
Subject: Re: best way to send parameters through more requests
One way can be to use the values in session and somehow explicitly delete
these attributes after they have been used.
Event listeners can I think help here. Just pump an
can write some tests on them so that it will not be "unmaintable"
Cheers
-Original Message-
From: Emilia Ipate [mailto:[EMAIL PROTECTED]
Sent: 09 June 2006 13:04
To: Struts Users Mailing List
Subject: RE: best way to send parameters through more requests
Using hidden fields is
One way can be to use the values in session and somehow explicitly delete
these attributes after they have been used.
Event listeners can I think help here. Just pump an event when you are done
with. This should delete the session attributes.
Any good patterns in this regard?? References?
> Usi
--Original Message-
From: Samere, Adam J [mailto:[EMAIL PROTECTED]
Sent: vrijdag 9 juni 2006 13:57
To: Struts Users Mailing List
Subject: RE: best way to send parameters through more requests
You also may be able to store state in hidden fields in the rendered
markup, or by encoding the raw binary
[mailto:[EMAIL PROTECTED]
Sent: vrijdag 9 juni 2006 13:57
To: Struts Users Mailing List
Subject: RE: best way to send parameters through more requests
You also may be able to store state in hidden fields in the rendered
markup, or by encoding the raw binary data in a single hidden field.
This goes a
, 2006 7:40 AM
To: user@struts.apache.org; [EMAIL PROTECTED]
Subject: RE: best way to send parameters through more requests
Also a word of caution I presume all the objects you store in session
are seriallizable. If they are not then your solution wont work if the
application is deployed on cluster
-Original Message-
From: Dave Newton [mailto:[EMAIL PROTECTED]
Sent: 09 June 2006 12:33
To: Struts Users Mailing List
Subject: Re: best way to send parameters through more requests
Emilia Ipate wrote:
> Is there a solution besides using session, to send some request
> parameters fr
Emilia Ipate wrote:
> Is there a solution besides using session, to send some request
> parameters from one request to another?
> I would like to implement something like a shopping cart (a
> functionality which needs about4-5 steps) and I do not want to store
> the objects in the session (it is al
Title: Message
Hello,
all!
Is there a
solution besides using session, to send some request parameters from one request
to another?
I would like to
implement something like a shopping cart (a functionality which needs about4-5
steps) and I do not want to store the objects in the session (i
22 matches
Mail list logo
