Nate Nielsen wrote: > There is currently a way > to specify a fuseaction simply by using a custom attribute, but with the > next release, that data will be encrypted and scrambled, making it > impossible to specify such a param.
No problemo. That just calls for something like this: <cf_fs_activeserver action="getAttributes"> <cfset dummy = StructAppend(attributes, activeserver, "no")> ...in app_globals, fbx_settings, or whatever. But yeah, I can see why you might want an answer for that question. > The server page also doesn't seem to fit into the FB model that I can > tell. > I suppose you could simply make it a regular fuse action or something... If the need of the client script was sufficiently narrow, sure. But I wouldn't create a stand-alone fuseaction for it if it could serve other purposes. For example, a fuseaction that returns a list of states to a client FScript could also return that same list as WDDX to another CF app, or with CFMX, to the caller of a web service. > ...realize there are no FusionScript "pages" - its all tags and API > calls. Understood. But there need not be a functional difference between: <cf_fs_dothis action="whatever"> ...and... <cfmodule template="index.cfm" fuseaction="dothis.whatever"> An FB app doesn't need to return pages full of HTML... it can be made up of nothing but calls to various custom tags, and can return data as easily as anything else. The only difference would be that you'd have a single wrapper (index.cfm) for all functionality, rather than a multitude of individual wrappers (fs_activeserver.cfm, fs_function.cfm, and so on). > I wouldn't port it into FB regardless because I would like to leave the > API > open to be changed to those whom are not familiar with FB. Makes sense. -- Roger ==^================================================================ 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 ==^================================================================
