Hey ccrashhh....

Long time no parler dude....comment ca va...

I agree - we just started our UAT and TRA - we quickly discovered this
to be an issue.

Glad to see someone else out there can replicate.

Have a good one eh...


On Jan 6, 8:52 am, ccrashh <[email protected]> wrote:
> They are certainly compatible (User 6.3 vs 7.1 Server)...with one
> annoying exception:  your forms and code will ALWAYS cache.  That's
> right...each and every time you open a form using User 6.3 on a 7.1
> Server installation of Remedy ARS, it will overwrite the existing arf
> and arv files.  Fun times.
>
> In as large an organization as I am in, it takes time to rollout
> certain tools.  We decided to upgrade the backend while the QA people
> dicked around with the 7.1 User tool.  They still haven't "approved"
> it for rollout, but we were assured by BMC/Remedy that things would be
> hunky-dory.  Not so much.  We have users all over the world, and many
> are now complaining that the application is so slow as to be
> unusable.
>
> We tested packet traffic using Wireshark and noticed that opening a
> form in Query mode with a 6.3 User tool on a 6.3 Server meant around
> 10 packets with a total size of about 1900 bytes.  Opening the same
> form in the same way against a 7.3 Server had 215 packets and about
> 190,000 bytes.  A factor in size of about a 100.  We then realized
> that the 6.3 User tool was forcing a constant recache of the forms/
> code.  Sigh.
>
> Just a heads up to any in a situation like this.  If Users are
> complaining about slow speeds with the arserver 7.1, check which
> version of the User tool they are using.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> Platinum Sponsor:www.rmsportal.comARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Reply via email to