Any idea how hard it would be
to roll your own web service code? It's just an XML
file that represents a value,
kind of like WDDX, right? I was thinking you could put
some code in your fbx_layouts
that takes a return value and outputs it as a web
service.
<cfif
not fusebox.isCustomTag>
<cfinclude
template="lay_webService.cfm">
</cfif>
Or have I vastly oversimplified
the problem?
Patrick
-----Original Message-----
From: Stacy Young [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 17, 2002 8:44 PM
To: '[EMAIL PROTECTED]'
Subject: RE: fuseboxed cfc'sThe switch was where I first started cause it looks like prime opportunity...but up until this point I haven't been able to justify it's purpose for two reasons:a) The whole reason I wanted it there was for exposing functionality (i.e. fuseactions) as a web service....but then I had no uniform structure as to how my application "serve" those up. i.e.(I believe u can create new mappings in the CF admin for each service but that's a manual process...eek)Anyway maybe someone else would have had a different approach but to me it wasn't really feasible.Now I have a "wrapper" CFC which acts as the "hub" or "factory" or "switch" within the model that farms out all the requests to sub portions of the model. As a matter of personal taste I have a model directory in my root like so:commyDomainreportsuserutilshomeCircuit1childCircuit1homeCircuit2childCircuit2This "com" directory has become my "corporate hierarchy" of objects from which I call from my FB apps as fuses. They're highly resuable and very granular in that additions and/or extensions won't disturb any dependancies. (this is done by extending the base class of objects I've created)Example I have a main Report CFC which is then extended into different report "types" which are CFCs in themselves. (Don't be fooled...I'm not THAT confident in whatI'm talking about here just yet hehe)Then my wrapper CFC would be in there somewhere and I'd create the 1 mapping in the CF admin like:(well in all honesty I haven't *done* a mapping yet - not even sure if it works)b) The second reason I found the CFC - SWITCH setup a little icky was that most of the functionality I ended up *wanting* to expose resides within the "model" portion of my application...*not* my fuseactions. (with occassional exceptions)I then started going off a on a crazed spree of making FB itself a CFC and have it inherit all it's circuits and a few other crazy ideas that either haven't panned out yet, didn't prove worthy of the complications, or I haven't had enough time to explore.In summary...I've got some new things going on but I think it's far from revolutionary.Cheers,Stace
==^================================================================ 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 ==^================================================================
