I don't know all the science to it Steve, however I believe it works like
you suggested. My logic for that is if something blows up in the tag (on a
separate thread), the page does not continue to process, its stops and
throws an error at you. This seems to me that the thread the calling
template is on must pause for tag processesing. To date, I haven't had a
threading problem. At the risk of being flamed by the god squad, I can tell
you that I have built 3 very large clustered adult sites in fusebox and 2
large financial websites. After the first one adult site I decided that I
was going to tagify every thing I could to shorten development time.
The reason for this was
a) There is a lot of processing code that is used site after site. As well
there are a lot of modules that are very similar. For me, tags and fusebox
take this reusable code and forge it into rapid development. It's been my
experience that each new app gives you atleast one new tag and/or one new
module that you can use for future sites thus cutting down future
development time.
b) I read somewhere there was a performance boost using tags as opposed to
includes
(unfortunately I am way to overwhelmed with work to do any real
performance testing and if people are arguing over 50 milliseconds, I will
take rapid development over production performance of 50 milliseconds any
day. To date I haven't lost any clients over performance issues.)
c) My personal preference is that tags make code look cleaner than includes
or processing done on templates. For instance the email thread about
header.cfm and footer.cfm, personally I do not think that looks right. My
personal opinion is that Allaire built Thistag.Executionmode for just this
purpose. Well you can do some other really cool things with the Thistag
scope but I use this method the most.
d) It's easier for me to change application logic if that logic is built
into small tags instead of big templates.
e) CF debugging used to spit heirglyphic errors at you and it was really
hard to figure out what line of what include the error was on. I found
tagifying processing cut down my debugging time.
So far as pausing tag processing, there isn't a Thistag.PauseMode, but you
can do some tricky things with the Thistag scope, CFASSOCIATE, WDDX, and
CFEXIT to emulate the same.
The reason I replied "What?" to your email was because I can think of
several instances where I send more than one variable from a tag to a
calling page, so I was actually asking what your logic behind doing so was.
----- Original Message -----
From: "Steve Runyon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 09, 2000 7:29 AM
Subject: RE: custom tags vs. cfincludes
> [Hi Sean! Enjoyed meeting you in DC!]
>
> All right, I have to admit my thread-ignorance here. Plus
> these answers are probably all in the manual, but I'll pick
> your brains instead. :-)
>
> Custom tags run on a separate thread, right? Could you ever
> run into problems (ie, run out of threads) if you used
> custom tags very, very heavily?
>
> I'm guessing that when the thread is spawned to run the
> custom tag it's spawned in synchronous mode, so that the
> spawning template pauses execution until the tag's thread
> ends. However, is this really the case? If so, can you
> control the mode?
>
>
> -----Original Message-----
> From: Sean Renet [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 08, 2000 10:37 PM
> To: [EMAIL PROTECTED]
> Subject: Re: custom tags vs. cfincludes
>
>
> >We also only return 1 variable from a custom tag and the variable
returned
> has the name of the file it called (minus the ".cfm").
>
> What?
> ----- Original Message -----
> From: "JME Maxwell" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, August 08, 2000 4:19 PM
> Subject: RE: custom tags vs. cfincludes
>
>
> > Custom tags allow you to encapsulate all your data.
> >
> > What happens in the tag stays in the tag.
> >
> > There is a slight performance issue, but I've been told it's very small.
> >
> > (Hal Helms did some benchmarks on his website, but I've no idea where
they
> > are).
> >
> > Our rule of thumb for development if it takes inputs or if it returns
> > information it is called as a custom tag. This gives us 100%
flexibility
> to
> > deal with any changes to graphics or functions without needing to worry
at
> > all about affecting the program downstream.
> >
> > We also only return 1 variable from a custom tag and the variable
returned
> > has the name of the file it called (minus the ".cfm").
> >
> > -----Original Message-----
> > From: Shane Witbeck [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, August 08, 2000 6:26 PM
> > To: fusebox
> > Subject: custom tags vs. cfincludes
> >
> >
> > Has anyone done any load testing or have any suggestions on whether to
use
> > custom tags vs. cfincludes? We are implementing a site which uses
several
> > custom tags and I was curious if there are performance issues with
respect
> > to using one over the other. TIA
> >
> > Sincerely,
> >
> > Shane Witbeck
> > Webmaster
> > mailto:[EMAIL PROTECTED]
> > www.digitalsanctum.com
> >
> >
> >
> >
>
> --------------------------------------------------------------------------
> --
> > --
> > To Unsubscribe visit
> > http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox
or
> > send a message to [EMAIL PROTECTED] with 'unsubscribe'
in
> > the body.
>
> --------------------------------------------------------------------------
> ----
> > To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
> >
>
> --------------------------------------------------------------------------
--
> --
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
> send a message to [EMAIL PROTECTED] with 'unsubscribe' in
> the body.
>
> --------------------------------------------------------------------------
----
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
