nal Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, July 26, 2004 9:15 AM
To: Struts Users Mailing List
Subject: Re: some best practices questions
One of our application had more than 300 screens, we used struts and
most of those screens had a drop-down list. We stored all
*data* caching should be done in the data
layer
> (like ibatis, hibrenate, whatever).
> .V
>
> Pilgrim, Peter wrote:
> >>-Original Message-
> >>From: Michael McGrady [mailto:[EMAIL PROTECTED]
> >>Sent: 08 July 2004 09:14
> >>To: Struts Users Mail
> -Original Message-
> From: Mike Duffy [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 19, 2004 10:45 AM
> To: Struts Users Mailing List
> Subject: Re: some best practices questions
>
>
> What do you think of caching static or semi-static data that
> applies
s, hibrenate, whatever).
> .V
>
> Pilgrim, Peter wrote:
> >>-Original Message-
> >>From: Michael McGrady [mailto:[EMAIL PROTECTED]
> >>Sent: 08 July 2004 09:14
> >>To: Struts Users Mailing List
> >>Subject: RE: some best practices questions
My comment would be that *data* caching should be done in the data layer
(like ibatis, hibrenate, whatever).
.V
Pilgrim, Peter wrote:
-Original Message-
From: Michael McGrady [mailto:[EMAIL PROTECTED]
Sent: 08 July 2004 09:14
To: Struts Users Mailing List
Subject: RE: some best practices
> -Original Message-
> From: Michael McGrady [mailto:[EMAIL PROTECTED]
> Sent: 08 July 2004 09:14
> To: Struts Users Mailing List
> Subject: RE: some best practices questions
>
>
> At 12:36 AM 7/8/2004, you wrote:
> >For this particular use case I would e
> -Original Message-
> From: Andrew Hill [mailto:[EMAIL PROTECTED]
> Sent: 08 July 2004 08:37
> To: Struts Users Mailing List
> Subject: RE: some best practices questions
>
>
> People seem to treat using the session as though it were some
> kind of moral
>
...
-Original Message-
From: McCormack, Chris [mailto:[EMAIL PROTECTED]
Sent: Thursday, 8 July 2004 22:37
To: Struts Users Mailing List
Subject: RE: some best practices questions
>users will fail over to another box with nothing in their session.
In some applications this is an acceptable risk if
unfortunately.
Chris McCormack
-Original Message-
From: Paul McCulloch [mailto:[EMAIL PROTECTED]
Sent: 08 July 2004 14:54
To: 'Struts Users Mailing List'
Subject: RE: some best practices questions
The solution to this problem is to use a load balancer which knows about
sessions.
ilto:[EMAIL PROTECTED]
> Sent: 08 July 2004 14:09
> To: Struts Users Mailing List; [EMAIL PROTECTED]
> Subject: RE: some best practices questions
>
>
> >3) Users session is on that machine. The url for that
> machine is machine123.msn.com.
>
> You missed a few steps w
}
>
> This is just an idea at this point, so I would welcome any
> feedback. I'm not sure if this will work or if its feasible, but at
> least it may generate some more ideas.
>
>
> - Original Message -
> From: Michael McGrady
> To: Struts Users Mailing List
> Sent: Tuesday,
ris McCormack
-Original Message-
From: Bryan Hunt [mailto:[EMAIL PROTECTED]
Sent: 08 July 2004 13:00
To: Struts Users Mailing List
Subject: Re: some best practices questions
The main arguments that people have against session storage is the following
a) Excessive memory consumption limits scallabilit
From: Christina Siena [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 8:16 AM
To: Struts Users Mailing List
Subject: Re: some best practices questions
I have an idea how to persist the data that I currently place in session
scope but I need to run it by someone.
Recall when I said that
At 12:36 AM 7/8/2004, you wrote:
For this particular use case I would either just use the session, or
alternatively I would just look up the dropdowns from db each time and
accept the performance hit, but its (probably) not worth the development
time - including ongoing maintenance - to do anything
just for
a few dropdowns.
my 2c
-Andrew
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, 8 July 2004 13:09
To: [EMAIL PROTECTED]
Subject: RE: some best practices questions
I think, performance wise File I/O is not the right idea.
What do you say ?
-
I think, performance wise File I/O is not the right idea.
What do you say ?
-Original Message-
From: Christina Siena [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 8:16 AM
To: Struts Users Mailing List
Subject: Re: some best practices questions
I have an idea how to persist
inal Message -
From: Michael McGrady
To: Struts Users Mailing List
Sent: Tuesday, July 06, 2004 11:59 PM
Subject: Re: some best practices questions
Ever thought about creating a new scope managed by your own manager from
application scope? That is an approach I have been thinkin
Your idea about creating a new scope sounds like an idea that might help. Can you tell
me more about it?
- Original Message -
From: Michael McGrady
To: Struts Users Mailing List
Sent: Tuesday, July 06, 2004 11:59 PM
Subject: Re: some best practices questions
Ever thought
I myself get caching with hibernate which I am using for persistance
but I wanted the more fine grained control like this so that I could page
back and forth using displaytag.org.
here is my jsp code for paging, hope this shows why I am doing it. I guess
my code is more for implimenting a clie
I, for one and one only, think that this sort of thing is directly
addressing the most common recurrent question on this list. So, if
anything, this de-spams the list. Thanks for the suggestion.
At 04:57 AM 7/7/2004, you wrote:
Sorry if this is considered spamming the list
Speaking of sto
On Wed, 07 Jul 2004 13:57:23 +0200, Bryan Hunt <[EMAIL PROTECTED]>
wrote:
For instance if I want to page through it ( using displaytags.org (10
out of 10)) or simply if I don't want to fetch
from the database time and time again.
By default the data expires on an hourly basis. And if a differe
Sorry if this is considered spamming the list
Speaking of storing stuff in session scope. I've developed what I think
is a handy class which I think it useful for
when I want to store something like a search in a session variable.
For instance if I want to page through it ( using displaytags
Thanks for the heads up, Rick. I think this whole area just needs a
concerted and orchestrated look. The standard approaches just are not
working for people. This is really so recurrent is more than recurrent.
At 09:59 PM 7/6/2004, you wrote:
On Tue, 06 Jul 2004 20:58:16 -0700, Michael McGrad
On Tue, 06 Jul 2004 20:58:16 -0700, Michael McGrady
<[EMAIL PROTECTED]> wrote:
I wouldn't mind an ongoing discussion group on this alone somehow, if
there were a way to do that. I might create a forum for that.
I created a model-struts group on yahoo groups for discussing more of the
model
lar
situations.
- Original Message -
From: Rick Reumann
To: Struts Users Mailing List
Sent: Tuesday, July 06, 2004 10:58 PM
Subject: Re: some best practices questions
Christina Siena wrote:
> I recently developed an application with a complex UI. One of the
> pages
I think the obvious is important with this recurrent problem. The obvious
is that you want to persist data for a period that is not coincident with
the normal devices for doing that. i.e. request, session and context
scopes. The difficulty is matching up with storage method on the server
with
session scope. I chose the third and wondered about some best practices others have
used in similar situations.
- Original Message -
From: Rick Reumann
To: Struts Users Mailing List
Sent: Tuesday, July 06, 2004 10:58 PM
Subject: Re: some best practices questions
Christ
Christina Siena wrote:
I recently developed an application with a complex UI. One of the
pages required querying the database based on user selection and
re-displaying the page with the retrieved data and any previous
existing user selections. Four different fields can trigger a db
query resulting
28 matches
Mail list logo
