...
| Facet Type Name | SffSeqeunceFacet |
|---|
| Language Support | Sequence Language | Code Block |
|---|
| language | xml |
|---|
| title | Sequence Language Example |
|---|
| linenumbers | true |
|---|
| <Execute eid="test" schedule="[30../10sec]" limit="15">
<Action>
<JavaScript>
sffLog.info("Doing something...");
</JavaScript>
</Action>
</Execute> |
|
|---|
| Transports | HttpServerExtensionArgs WsServerExtensionArg |
|---|
| Usage | Facet Types are used using <NewFacetInstance> when creating a Package (Deployment) definition for your models. | Code Block |
|---|
| language | xml |
|---|
| title | SffSequenceFacet Example |
|---|
| linenumbers | true |
|---|
| <NewFacetInstance fid="seq" name="seq" type="SffSequenceFacet">
<OnActivate>
<!-- Schedule something at the time of activation -->
</OnActivate>
<OnOpen ModifyPipeline="WsServerExtensionArgs"/>
</NewFacetInstance> |
|
|---|
| Use Cases | - Scheduling of tasks at given interval and frequency.
- Schedule Format is: StartTime..EndTime/Interval Where StartTime and EndTime can be a hierarchical dot-delimited format.
Example of dot-delimited format:
2015.MAY.25.14.30min means 2015-May-25:14:30. It is not necessary to specify time units on each element as long as there is at least one and you follow the standard time interval hierarchy (i.e. year-month-day-hour-minute-second-millisecond). In the above example, “MAY” is used by the system to match all the numerals with time units (i.e. it recognizes that if MAY is a month then to the left of it must be the year and to the right must be day, hour, minute etc.). For non-standard definitions, you can always specify time unit explicitly (e.g. 2015yr.128doy.15hr, where 2015 is a year, 128 is day of the year and 15 is hour of the day). Only 24 hours format is currently supported.
|
|---|
Static Files
Static Files Facet Types allows users to serve static files using A-Stack
...