Hi,

When I am not logged into CMS WBC, why does the system still make
40k's worth of calls for CSS and JavaScript files, such as those
below:

wbc.css
JavaScriptUIStrings.js
OptionsClient.js
Dates.js
Windows.js
CommonClient.js

I know these will cache at the user end but surely it doesn't make
sense to reference them on every page when are they are not required?

[ Post a follow-up to this message ]

Hi,

on my box it does not do this.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Tools" <mbrocklehurst@hotmail.com> wrote in message
news:e571bea.0404280555.57431b64@posting.google.com...
> Hi,
>
> When I am not logged into CMS WBC, why does the system still make
> 40k's worth of calls for CSS and JavaScript files, such as those
> below:
>
> wbc.css
> JavaScriptUIStrings.js
> OptionsClient.js
> Dates.js
> Windows.js
> CommonClient.js
>
> I know these will cache at the user end but surely it doesn't make
> sense to reference them on every page when are they are not required?

[ Post a follow-up to this message ]

Strrange, I get this on every page:

<!-- Inserted by Content Management Server: BEGIN EmbedTmplHeadHook
-->

<link rel="stylesheet"
href="/NR/System/WBC/Customizable/WBC.css">
<script language="JavaScript"
src="/NR/System/WBC/Customizable/WBCFuncPagesConfig/UIStringConstants/JavaSc
riptUIStringsNR.js"
type="text/javascript"></script>
<script language="JavaScript"
src="/NR/System/WBC/Customizable/OptionsClient.js"
type="text/javascript"></script>
<script language="JavaScript"
src="/NR/System/WBC/Internals/Shared/Dates.js"
type="text/javascript"></script>
<script language="JavaScript"
src="/NR/System/WBC/Internals/Shared/Windows.js"
type="text/javascript"></script>
<script language="JavaScript" type="text/javascript">
<!--
var IDS_FRAMEWORK_VIRTUAL_PATH =  "/NR/System/WBC";
// -->
</script>
<script language="JavaScript"
src="/NR/System/WBC/Internals/Shared/CommonClient.js"
type="text/javascript"></script>
<META name="ROBOTS" content="FOLLOW,INDEX">

[ Post a follow-up to this message ]