Re: [Modus-devs] Re: New Code Posted

[Jeremy F. <jfi...@ma...>]

Just an update: got the application-scoped library cfc working, so this =
is a possibility.=20
  ----- Original Message -----=20
  From: Jeremy Firsenbaum=20
  To: mod...@li...=20
  Sent: Thursday, November 14, 2002 5:36 PM
  Subject: Re: [Modus-devs] Re: New Code Posted


  Well, I just confirmed this. The included UDFs are not available to =
custom tags. This leaves us with a big decision.

  One of Nathan's concerns when discussing the UDF was approach was =
defining a namespace for Modus. I think this is a more powerful argument =
for the static CFC library than custom tag access. Seems to me that =
custom tag developers should be used to scope issues as these were the =
first real way to do encapsulation with CF.=20

  I really prefer the modus prefix on the functions as it defines a =
clear namespace for the API. One of the things I'm working on now is an =
application-scope cfc to hold the API functions. This is similar to the =
example I gave earlier where server.modus.udflib is referenced as modus =
in Application.cfm. Custom tag developers would need to use the full =
path in this case.

  As for many applications not using the cfapplication tag, that's news =
to me. The whole framework depends on the application name to allow =
various Modus apps to be run concurrently on the same server without =
name conflicts. Look at the way the registry constructs the components:

  server.modus[appName].persister[componentName];

  The UDF lib uses the applicationname to find the appropriate facade to =
call. This is why I'm looking into making the UDF lib a static =
application CFC. The loss of pageContext bug prevents CFCs from =
accessing the application scope. Each application would have its own =
static lib that maintains the applicationname in the instance scope. =
Thus normal page calls would look like modus.get() and custom tags would =
need to do application.modus.udflib.get(), or whatever the static lib =
winds up being called.=20

  If there's another way of doing this and still preventing name =
conflicts (my pressrelease and your pressrelease on the same server) =
then shout it out. This is crucial to the way Modus gets used so we =
should take the time to get it right.

  -Jeremy
  https://lists.sourceforge.net/lists/listinfo/modus-devs