Well, an API is an API is an API (something that 'hooks' a db for exchange of
data). Libraries/classes/?? are 'frameworks' that query the db(s). Using PHP
(or other web app) is the preference of whatever can call any API, eh? The rest
of the web publishing will be web app functions and the basics: HTML/CSS/JS.
IF (when?) I switch to using Data API, (for data exchange) there will likely be
more JavaScript usage in the websites, but there will still be a web app that
can send/make the call(s).
I guess the questions:
1) _will_ the other API's be killed (XML?, ODBC?, ??)
2) if they are not "killed", will they be switched to the same model as the
Data API (pay-to-play)?
NOT placing any bets, of course. :)
And I still speak SQL dbs for web publishing, so there's that. :)
Sorry, if that did NOT help, Joel!
Beverly
On Feb 15, 2018, at 1:57 PM, Joel Shapiro <info@xxxxxxxxx> wrote:
Hi all
Now that this list is awake again, I thought I’d ask a question:
What plans (or thoughts) do you have for when FileMaker eventually removes*
the XML API/WPE from FMServer?
- Remain on a version of FMS that still has XML (i.e. stop upgrading)
- Keep writing PHP but switch to using the new Data API
- Switch from PHP to some other language with the Data API
- Switch away from FileMaker
- Hope that the XML never actually gets taken out
- Other…
*NOTE: The XML API has not yet been deprecated, and will presumably remain in
at least the next couple/few/… versions of FMS. (Runtimes have been
deprecated for years but not yet removed.)
-Joel
