PHP can use the PHP API for filemaker, which uses the web publishing engine.
Java uses JDBC, which requires a connection to be configured and drivers installed to the filemaker database.
Both support create/edit/delete operations with filemaker data. The PHP API also supports other things like the execution of scripts and more complex logical functions.
For e-commerce, PHP is probably the way to go. You can call and parse your data in realtime, no need to store or cache data on the web side.
"capacity" may be the difference:
xDBC is 'tested' to 50
CWP (php) is 'tested' to 200
In 'real world' these may be more depending on various factors.
PHP can use the FileMaker API for PHP or even the ODBC or XML without the API.
My first advice is to USE WHAT YOU KNOW. If you have a web app that uses the xDBC, then that goes into the "+" column. If you know PHP and can step outside the API for functions that might be needed, use that.
NodeJS w/express can do this on the server side.
Awesome! do you have some links to documentation?
1 of 1 people found this helpful
... or one can write own calls using HTTP Node.js v6.2.1 Manual & Documentation
And here it looks like somebody made a complete angular fm implementation: GitHub - 360works/fmangular: FileMaker tools for Angular
More is not necessarily better; usually less is more. The most important thing is availability of useful examples.
My choice in that way has been AngularJS and NodeJS. I'm a bit hesitant about the TypeScript requirement of AngularJS 2 so I might jump to a different framework unless there is suddenly a just as friendly ECMA version popping up eventually.
Still trying to work all that out Sails seems to offer rather complete structure and great documentation to go with it.
Thanks for the feedback on an important topic.
Sent from my iPad
What's your editor I seem to lean towards Atom
Again to many choices!
Sent from my iPad
There has been only 1 - one real text editor for me since I started using text editors in 1991 or so; I have tried others, there are many good ones, however vim is not a text editor it's a fully configurable developer environment. I have been lead into "heathen" activity throughout, such as CodeWarrior( Mac Classic, ) XCode( MacOS X, ) CygnusEd( AmigaOS ) and BBEdit Lite.
The people who wrote vim claims it's a text synthesizer.
Some people say it's a good choice not to use it as pr say... as it's "old" and "dated" then again yet it's the best tool out there to get the job done IMO.
Of the GUI editors I have tried Notepadqq, Notepad++, BBEdit Lite, TextMate, and Microsoft VS Code; not to mention my all time favorite Fraise, but all of them lack the functions I have in vim :-(
Yet those are all good for editing config files...
There is a really nice tool for the Mac though; in the case of working with XML it's called XMpLify