Typical Omission?: Client Side Caching Support - AribaWeb (aribaweb.org)

Message from discussion Typical Omission?: Client Side Caching Support
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Feb 2009 09:44:35 -0800 (PST)
In-Reply-To: <1BA5F481-E99A-4BC1-A30C-805719E53C53@gmail.com>
References: <4589b491-a5d7-4d09-b21d-5b8fbaccc42c@q9g2000yqc.googlegroups.com> 
	<1BA5F481-E99A-4BC1-A30C-805719E53C53@gmail.com>
User-Agent: G2/1.0
Message-ID: <c2dfbdcb-caa3-4820-a1cc-6382702311ba@z1g2000yqn.googlegroups.com>
Subject: Re: Typical Omission?: Client Side Caching Support
From: luxspes <luxs...@hotmail.com>
To: "AribaWeb (aribaweb.org)" <aribaweb@googlegroups.com>

All right, so it is not possible to do it now... (and by what you
said, it will not be possible to do it in the near future)

Now, lets say I  have already built my app using Ariba and I  have a
very important ($$$) customer that really wants this feature (you
probably know how irrational some customers can be about some
features).

What would you recommend me to do  to make my customer happy? Perhaps
creating an specially designed "combobox tree control" with inherent
caching/chaining capabilities encapsulated inside it?

Would it be hard to create such a "low level" new control in AribaWeb?

Regards,

LuxSpes


On Feb 24, 10:03=A0am, Craig Federighi <craig.federi...@gmail.com>
wrote:
> Hi LuxSpecs,
>
> We wouldn't call it an "omission" as much as a "design choice"... :-)
>
> We don't cache this data on the client because, in the general case, =A0
> we can't detect that it's statically cacheable. =A0(e.g. your code may =
=A0
> be filtering this list the second time around based on other =A0
> selections on the page or other changes in server-side state). =A0In =A0
> practice we have not found this to be a significant issue in =A0
> application responsiveness or user experience.
>
> > =A0want it to use that as a
> > cache and do not go for them until I tell it to do so?
>
> That last part is exactly the issue: we don't want your programming =A0
> burdened with needing to "tell it to do so" -- this leads to a lot =A0
> more code and a lot more opportunities for errors.
>
> Thanks!
>
> - craig
>
> On Feb 24, 2009, at 7:26 AM, luxspes wrote:
>
>
>
> > Hi!
> > It seems like a simple problem, but it is not (to day, I have not been
> > able to find a way to do this without complex javascript coding):
>
> > You have chained comboboxes: County and State.
>
> > You select USA in the Country combobox, and its 50 States are loaded
> > in the States Combo (roundtrip to the server to fetch them)
>
> > You select Mexico in the Country combobox, and its 32 States are
> > loaded in the States =A0Combo (roundtrip to the server to fetch them)
>
> > Now you select USA in the Country combobox again... how do I tell
> > Ariba that I do not want it to go to the server for them, since it
> > went for them the last time I selected USA, I want it to use that as a
> > cache and do not go for them until I tell it to do so?
>
> > Regards,
>
> > LuxSpes