> CF mappings require that there is a leading slash to call them.  This is
> a problem is FuseQ and FB3 as they don't let you put a slash in there
> (in fact the delimiter is a slash - I think a pipe (|) or comma would
> have been better.:

that's got nothing to do with FuseQ, it has to do with the core file as
specified

> John, despite the fact it looks like 0-60 in < 60 secs, its not the case
> - we have been looking at this issue for a while now!

I'm still trying to figure out what you mean with the slashes. SInce the
articles on how to use FuseQ for bubbling error/exception handling, layouts
fuses, content components, and Security are not available on the site, I'm
just wondering what you can base your conclusions on (?)

> Your solution is to define a new mapping that for a physical location,
> to make it appear that the one physical location has multiple physical
> pseudo-locations.

again, I must just be an idiot. But the answer is no. FuseQ (and the FB3
core for that matter) require no definition of mappings for physical
location. Only the circuits get mapped, as per FB3 standards. But your
definitions of circuits are also mapped, so it looks like apples and apples
to me, "you say tomato, and I say tomatoe" (oops, that song doesn't work
when typing)

> That's cool.  I'm just not thrilled about having to
> define new CF-wide mappings.  In general, I only have two mappings on my
> server, "/" and "CustomTags".

hmm, I don't use any mappings at all with any of my FB3 apps. The "/" comes
built-in , so to speak, mapped to the web server, so that doesn't count. But
there is no need to have a CF mapping for a CustomTags directory at all,
that can be handled with a single local scope variable in a fbx_settings
file.

==^================================================================
This email was sent to: [email protected]

EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]

T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================

Reply via email to