ThePort's Product and Technology blog. We'll share helpful tips about the platform, talk about upcoming releases, and maybe on occasion share a story or two on how awesome the team is here.
Trigger vs. Process Server Module
Just a quick helpful hint on something I've been asked a few times of late. When executing a server module in our XSLT template system, you can do it one of two ways:
ProcessServerModule or TriggerServerModule
The difference between the two is subtle, especially if you're looking at it from the user's perspective. But under the hood, the different is definitely noteworthy.
ProcessServerModule
You want to use ProcessServerModule in most cases. This logic does the processing at the server and sends the output down as rendered HTML to the client. If you view source, you'll see the HTML of the module
TriggerServerModule
The TriggerServerModule is also rendered on the server, however, instead of sending rendered HTML down to the browser, it sends an AJAX call that can be triggered by some event (onClick, onBlur, etc). So if you do a view source, you'd only see the AJAX call and not the rendered output. This is a handy method to use if you're loading modules hidden behind tabs or other event driven code.
