Too many functions!!!

Question

While developing a large FMS application, main.asc has become
more than a bit lengthy. The bulk of the file is taken up by the
custom client functions that are created anonymously under the
onConnectAccept function.
(ex
newClient.myFunction = function(param1, param2) {
//do stuff
I tried splitting some of the (hundreds of) functions into
seperate files then I used load() under the onConnectAccept
function. I think since these functions are created during runtime,
the load function is not appropriate (triggered on compile time).
Is there some way to split these functions into seperate
files?

Answer 1

Yup... until we get AS2 support in FMS, prototypes seem to
save the day. The client class is sepcial in it's auto resolve
functionality, and I'd imagine that's due to some good thinking on
the dev team's part.
Using the prototype also has the benifit of making the client
object smaller. When you apply a funtion directly to the client,
the function becomes part of each client object, wher with a
protoptype function it does not.
In application where you might return the entire client
object to a client (ie user data sent to an admin user), all of the
functions that are applied to the clients travel along with the
data, creating much more data transfer than is necessary. By
prototyping the function, it does not travel with the client
data.