![]() We tend to use the state labels stopped, stopping, running and starting. When Lucee is determining in which state an EG is, it will call the getState() method of the EG CFC. The state is the label displayed when the EG is stopped or started or when it is about to start. So for instance if you want to define the above configuration with the Event Gateway Driver CFC the CFC might look like this:ĬustomLoggerDriver.cfc component extends="Gateway" The basic Gateway driver is defining the edit fields for the configuration in the administrator. The gatway driver is a CFC that is allowing you to configure your EG. There are 2 components that are important for writing an event gateway: What are the involved components in Lucee? Just use the according JAR solution available for the specific event (like SMS or others). ![]() Some parts sometimes still need perhaps a Java library, but coding around that normally is not really a problem. ![]() In Lucee EG’s can be written in CFML and this is what this description is all about, which now makes it way more attractive to write the decisive parts with your favorite language. Given this downside, it is understandable, that there are such few available event gateways available. The main reasons were the lack of diversity and implementations which were due to the fact that EG’s had to be written in Java and not every CFML developer is very familiar with Java. So you basically have an event producer and an event consumer.Įvent Gateways have for a long time lived a quiet life in CFML for several reasons. For instance if an SMS is sent to the server asking for the current heap memory space, the server could respond with an SMS returning the details. What then can be done with these events is to trigger some actions that react on these events. These kind of events could be something along the lines of:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |