Single Library vs Multiple Libraries

[James Fuller]

Single Library vs Multiple Libraries

Currently we're in an environment that was set up with a single ISF Library.  However, over the last 3 years in which we've been using this library, it has become quite bloated and oversized for a .js file.

We are looking for best practices on reducing file size.  We have thought about creating service specific libraries or something along those lines.

Can anyone provide what type of approach they've used?

[Jeffrey Wood]

We've moved away from using a single ISF file for all services.  Right now we've got the standard custom file which contains common ISF functions used by all services.   Then we've broken out specific functionality for service categories into their own custom ISF files.

For example, all of our ISF for ID services are in their own seperate .js file.  This helps break up the size of the file but also is handy when you have multiple people working on Service Design.

As we mov

[James Fuller]

To reduce the overhead on the client (javascript being client-side), we would like to be albe to dynamically attach the library to be used by service.

 For instance, when the user selects a service, the loader will only load a library specific to that service.  However, we don't want all service libraries loaded on every service.

The goal of this being that minimal code/libraries have to be pushed to the client, thus reducing load times for our "big" services and h

[James Fuller]

In relation to having multiple libraries, how do you attach all of the field level scripting for an individual service?

Do you have an automated attach routine or do you manually attach scripting?

I have been able to come up with a method to automatically attach a script library associated only with a particular service, but I'm still working on trying to update our automated attach routine to create/attach the field level functions.  Any insight someone would have in this area would be