What’s new in 5.6.1
- HTTP Channel API to manage channels programmatically
- The ability to call queue.push{} multiple times within a message filter
- Added a built-in trace() function added to the Translator
- The node.setNodeValue() method has been added to the node API
- The ability to connect to an external authentication source
- The ability to process multiple HTTP requests concurrently in a single channel
- You can now restart built-in web server without restarting Iguana
- Added the ability to call C/C++ functions in a DLL from Lua, see: Writing a native extension Lua DLL in Iguana using C/C++
- Several other new features
- Several bug fixes, and behavior changes
- To see the complete list of changes, feel free to browse the Iguana change log
HTTP Channel API to manage channels programmatically [top]
Added the HTTP Channel API which provides the ability to create, update and manage channels programmatically.
Additional Information
- HTTP API Reference: channel
- Lua Module API Reference: iguanaServer.lua
- iguanaServer.lua – Manipulate local or remote Iguana channels from the comfort of the Translator a Lua wrapper script that utilizes this API
The ability to call queue.push{} multiple times within a message filter [top]
You can now call queue.push() multiple times from any component script, an example where this is useful is when splitting a complex message into several smaller messages.
The queue.push() function works in three types of component: Filter, From Translator, and From HTTPS. Previously you could call it multiple times in a From Translator, and a From HTTPS but only once in a Filter component. This is behavior has been updated to allow multiple calls from a Filter component script.
Additional Information
Added a built-in trace() function added to the Translator [top]
A built-in trace() function has been added to the Translator so you no longer need to declare an explicit trace() function in each module.
This new trace() is more convenient and more versatile than hand-coded version:
- You don’t have to declare it
- It takes any number of parameters
- It doesn’t show empty parameters as nil
The old way:
The new way:
Additional Information
The node.setNodeValue() method has been added to the node API [top]
The node. method has been added to the node API to enable modification of a node value without having to navigate to that node from the parent.setNodeValue()
This is a fairly subtle issue that was identified by one of our users. Basically he was passing a leaf node to a function and there was no way to update it, as you could only manipulate child nodes.
A picture is worth a thousand words:
Additional Information
- node.setNodeValue() in the node API reference
- FAQ: Using node.setNodeValue() to manipulate node values directly
The ability to connect to an external authentication source [top]
This means you can use Iguana’s built-in authentication (the default) or connect to an External Identity Store to validate user logins. The use of an External Identity Store in Iguana is optional, and defaults to disabled. When this feature is enabled, Iguana will query the External Identity Store first and then revert to using the local Iguana validation if the external validation fails.
Additional Information
- Settings: Manage External Authentication
- How do I use an External Identity Store for Authentication?
The ability to process multiple HTTP requests concurrently in a single channel [top]
Iguana can now process multiple HTTP requests concurrently in a single channel. The feature is configured via the ThreadCount setting in a From HTTPs channel configuration.
Additional Information
You can now restart built-in web server without restarting Iguana [top]
You can now restart Iguana’s built-in web server from the command line when the Dashboard is not accessible. Usage: ./iguana --restart_webserver (at the command line).
Simply navigate to the Iguana install directory and then issue the command:
