The release of DayBack for FileMaker last month has started a very exciting time for us here at SeedCode! Bringing the Calendar to a new code base and seeing it successfully deployed in the real world has been nothing short of thrilling. We’ve recently added mobile support and are looking forward to the future enhancements of DayBack for Pro and Go.
- FileMaker Server is a powerful tool, and it can do a lot. However, this ability to multi-task tends to lead to deployments where it’s simply trying to do too much. On the web publishing side things like portals on target layouts, server side scripting, huge data sets, etc. often put a considerable load on the server. Can we architect DayBack to do this kind of work in the browser and therefore put a lighter load on our FileMaker Server?
- Supporting server side processes requires a different level and type of support than client side ones. This is not just the case for FileMaker Server, but any server based application. Supporting the server often requires working on a specific machine with specific issues that extend well beyond your app, web servers, permissions, program versions, etc. can all affect how things run. By minimizing our server side footprint we hope to minimize the need for this kind of support.
Here is what fmxj lets you accomplish:
- Build complex queries and perform HTTP POSTs to your FileMaker Server.
- HTTP POSTS can be done directly to the FileMaker Server’s XML WPE or a simple PHP relay can be used to get around cross-domain issues and provide more authentication options.
As always, we love to take any opportunity we have to share our code, and I’m personally looking forward to keeping you posted on our progress.