Couldn't I just use the built in web publishing capabilities of FileMaker Server to do the same thing?

Not really because Reactor is tied very closely to the client and interacts with the client context extensively. This gives our controls the smooth tightly integration needed.

For some of the controls you could achieve a similar effect using custom web publishing from FileMaker Server, but there are some major differences:

Response time: Reactor is virtually instant because it updates data from the local client, whereas an update written to the server takes up to a second to be "seen" by the client. This makes possibilities such as the live portal filtering impractical via the server.

Serving: Reactor serves content directly from a calculation and/or container fields. This makes deployment so much simpler and easier.

Script running: Reactor can trigger a script on the users machine.


Submit Question

No luck in the FAQ? Complete the form below to submit your question to our technical support.