FM-PHP-API The only API/Plug in available?

25 messages Options
Embed this post
Permalink
1 2
Jorge Biquez

FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
Hello all.

I hope these not sound like stupid questions...anyway here they go....

While in the process of studying the FM-PHP doc and trying to read
everything I can found on the subject some questions arrived to my mind...

- Is the FM-PHP-API the only one plug in / API supported for managing
FM Databases on the web? (I know can be done with XMl, XLST without
the API and with Lasso (in my case Lasso didn't worked on my
configuration and I could not test it)).

If I use VB6 or Delphi or C is there any way to interact with FM
databases in similar ways and commands that the API offers and not
only with ODBC with SQL?

- Is the format of FM (8 and above) too obscure that it is almost
imposible or hard to develop those kinds of API/Plug In?

I Have some clients of small companies that invested on FM5/FM6
Server and that have applications that are running real fine but
would like to do some deployment of information or be able to give
access over the Internet to clients or providers to their process.
For those kind of clients......

- The only path to follow is to upgrade ALL to FM9 or above and move
to the PHP-API ? (almost forbidden for the cost of licenses and the
job involved)

I have been working with FM since version 4 and each time licenses
have increased their cost. For medium/small companies FM is the
correct solution but when they want to increase in volume and number
of users is where they can not continue growing. That's why it is
very attractive to be able to use the Internet with their actual developments.

Any comments based on your experience with similar projects?

Thanks in advance.

JB

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Tim 'Webko' Booth

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
Dear Jorge,

>
> - Is the FM-PHP-API the only one plug in / API supported for  
> managing FM Databases on the web? (I know can be done with XMl, XLST  
> without the API and with Lasso (in my case Lasso didn't worked on my  
> configuration and I could not test it)).

No - I use the FX.php class quite happily, which also plugs in through  
the XML stream, which has been available since at least FM 5.5 (when  
did XML become a supported format? Since then...)

>
>
> I Have some clients of small companies that invested on FM5/FM6  
> Server and that have applications that are running real fine but  
> would like to do some deployment of information or be able to give  
> access over the Internet to clients or providers to their process.  
> For those kind of clients......
>
> - The only path to follow is to upgrade ALL to FM9 or above and move  
> to the PHP-API ? (almost forbidden for the cost of licenses and the  
> job involved)

No.

If they're on FM5/6, then CDML is still an option (if you can find a  
copy of FM Unlimited these days...)

FX.php is effectively free and can be used on any XML enabled  
FileMaker system, although the exact set up will vary quite  
considerable depending on exactly which versions are being used.

You're not tied to the API, although I would suspect that future  
releases will have more and more goodies bundled with the API rather  
than being developed for any other approach/web technology.

Cheers

Webko

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Corn Walker

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Jorge Biquez
On May 27, 2008, at 12:51 AM, Jorge Biquez wrote:

> Any comments based on your experience with similar projects?

A couple...

First, APIs:

There is a plug-in API available but I'm not aware of any that  
interact with other programs to the scope you're describing. For FMP  
9 there's the XML/XSLT interface, ODBC/JDBC, the PHP API for FMP, and  
Applescript (I may be forgetting something). Third parties have  
provided the FX.php API, a VB.Net API, a Ruby API, a Python API, and  
there are other technologies that leverage the available APIs (such  
as Lasso).

Second, cost:

Your clients, unless really really small, should have a volume  
license agreement. This permits them to add seats in a cost effective  
way. They can also subscribe to maintenance which gets them newer  
versions of the product when released. If they literally can not  
afford to hire an additional person because of the FMP license then I  
don't think they can be helped. I can't imagine a scenario where a  
couple hundred dollars would make or break a company.


Cheers,
-corn


Corn Walker
The Proof Group
http://proofgroup.com/

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Ibrahim Bittar Torres

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
On 27/05/2008, at 06:12 AM, Corn Walker wrote:

> I can't imagine a scenario where a couple hundred dollars would make  
> or break a company.

Then you need to come to Mexico... LOL

Just kidding but I also see this "limitation", not in FileMaker (nor  
any other software) but in people's minds.

It's more a cultural problem rather than a technical one because  
people feel that any amount, any, is too much paying for "a software"  
and they prefer to spend their money in a new machine which costs a  
couple hundred thousand dollars or in a vacation trip.

Anyway, every region has its own problems. This is one of ours...

Just my 2¢ of mexican pesos.

Saludos

Ibrahim Bittar Torres
Director General
Eikonsys
FileMaker 9 Certified Developer
http://www.eikonsys.com
FileMaker Business Alliance





_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Ibrahim Bittar Torres

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Corn Walker
By the way, if you want to provide FM licensing to your customers and  
you have a commercial solution already created then you can apply for  
the SBA (Solution Bundle Agreement) program.

FileMaker would sell you licences at a VERY special price provided  
that you include them with your solution and not sell them separately.

For more details you can contact Mike Alvarado at FMI: [hidden email]

Saludos

Ibrahim Bittar Torres
Director General
Eikonsys
FileMaker 9 Certified Developer
http://www.eikonsys.com
FileMaker Business Alliance



On 27/05/2008, at 06:12 AM, Corn Walker wrote:

> On May 27, 2008, at 12:51 AM, Jorge Biquez wrote:
>
>> Any comments based on your experience with similar projects?
>
> A couple...
>
> First, APIs:
>
> There is a plug-in API available but I'm not aware of any that  
> interact with other programs to the scope you're describing. For FMP  
> 9 there's the XML/XSLT interface, ODBC/JDBC, the PHP API for FMP,  
> and Applescript (I may be forgetting something). Third parties have  
> provided the FX.php API, a VB.Net API, a Ruby API, a Python API, and  
> there are other technologies that leverage the available APIs (such  
> as Lasso).
>
> Second, cost:
>
> Your clients, unless really really small, should have a volume  
> license agreement. This permits them to add seats in a cost  
> effective way. They can also subscribe to maintenance which gets  
> them newer versions of the product when released. If they literally  
> can not afford to hire an additional person because of the FMP  
> license then I don't think they can be helped. I can't imagine a  
> scenario where a couple hundred dollars would make or break a company.
>
>
> Cheers,
> -corn
>
>
> Corn Walker
> The Proof Group
> http://proofgroup.com/
>
> _______________________________________________
> FMPexperts mailing list
> [hidden email]
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
>

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Jorge Biquez

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Tim 'Webko' Booth

>
>No.
>
>If they're on FM5/6, then CDML is still an option (if you can find a
>copy of FM Unlimited these days...)

Yes CMDL it is an option ...limited if you want to connect to other
systems with other web services (Apache, IIS, etc) and have only one
web serving all the web pages....



>FX.php is effectively free and can be used on any XML enabled
>FileMaker system, although the exact set up will vary quite
>considerable depending on exactly which versions are being used.
>
>You're not tied to the API, although I would suspect that future
>releases will have more and more goodies bundled with the API rather
>than being developed for any other approach/web technology.
>
>Cheers
>
>Webko
>
>_______________________________________________
>FMPexperts mailing list
>[hidden email]
>http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au

Thanks for the comments

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Jorge Biquez

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Corn Walker
Hello all.
At 06:12 a.m. 27/05/2008, you wrote:

>On May 27, 2008, at 12:51 AM, Jorge Biquez wrote:
>
>>Any comments based on your experience with similar projects?
>
>A couple...
>
>First, APIs:
>
>There is a plug-in API available but I'm not aware of any that
>interact with other programs to the scope you're describing. For FMP
>9 there's the XML/XSLT interface, ODBC/JDBC, the PHP API for FMP, and
>Applescript (I may be forgetting something). Third parties have
>provided the FX.php API, a VB.Net API, a Ruby API, a Python API, and
>there are other technologies that leverage the available APIs (such
>as Lasso).

Anyone can comment on these API's based on experience?

They all sound very interesting.

JB

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Jorge Biquez

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Ibrahim Bittar Torres
Hello.

Thanks a lot for theinformation. Will contact him today to see prices. :=)

JB

At 07:44 a.m. 27/05/2008, you wrote:

>By the way, if you want to provide FM licensing to your customers and
>you have a commercial solution already created then you can apply for
>the SBA (Solution Bundle Agreement) program.
>
>FileMaker would sell you licences at a VERY special price provided
>that you include them with your solution and not sell them separately.
>
>For more details you can contact Mike Alvarado at FMI:
>[hidden email]
>
>Saludos
>
>Ibrahim Bittar Torres
>Director General
>Eikonsys
>FileMaker 9 Certified Developer
>http://www.eikonsys.com
>FileMaker Business Alliance
>
>
>
>On 27/05/2008, at 06:12 AM, Corn Walker wrote:
>
>>On May 27, 2008, at 12:51 AM, Jorge Biquez wrote:
>>
>>>Any comments based on your experience with similar projects?
>>
>>A couple...
>>
>>First, APIs:
>>
>>There is a plug-in API available but I'm not aware of any that
>>interact with other programs to the scope you're describing. For FMP
>>9 there's the XML/XSLT interface, ODBC/JDBC, the PHP API for FMP,
>>and Applescript (I may be forgetting something). Third parties have
>>provided the FX.php API, a VB.Net API, a Ruby API, a Python API, and
>>there are other technologies that leverage the available APIs (such
>>as Lasso).
>>
>>Second, cost:
>>
>>Your clients, unless really really small, should have a volume
>>license agreement. This permits them to add seats in a cost
>>effective way. They can also subscribe to maintenance which gets
>>them newer versions of the product when released. If they literally
>>can not afford to hire an additional person because of the FMP
>>license then I don't think they can be helped. I can't imagine a
>>scenario where a couple hundred dollars would make or break a company.
>>
>>
>>Cheers,
>>-corn
>>
>>
>>Corn Walker
>>The Proof Group
>>http://proofgroup.com/
>>
>>_______________________________________________
>>FMPexperts mailing list
>>[hidden email]
>>http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
>
>_______________________________________________
>FMPexperts mailing list
>[hidden email]
>http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au


_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Bob Patin

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Tim 'Webko' Booth
Jorge,

I echo what Tim has said about FX.php; keep in mind that neither the  
FM API nor FX.php are plugins, per se, but rather a set of PHP  
libraries that you use to interact with FileMaker's Web Publishing  
Engine.

I can't imagine considering CDML at this point, although I wrote a lot  
of sites with it (in fact, Tim was my best source of help when I got  
stuck). Most FileMaker hosting companies are moving away from hosting  
CDML sites; we had over 100 databases using CDML at one time, and now  
we have only 9, mainly because we've migrated most of these to  
FileMaker 9.

In tests run by other consultants, FX.php came up approximately 8x  
faster than the FileMaker API; these are not my numbers, as I've never  
done any testing.

As to which is easier to learn, that's a toss-up; I've been doing FX a  
lot longer, so I prefer it probably because I'm more proficient with  
it than with the API, but both achieve the same results, just using a  
different method. However, once you get familiar with PHP, you can  
work in both as needed.

As Tim pointed out, unless you want to upgrade to at least FileMaker 7  
(which you'd have a hard time finding), FX.php is your only option for  
PHP interfacing with FileMaker.

Best regards,

Bob Patin
Longterm Solutions
[hidden email]
615-333-6858
http://www.longtermsolutions.com
FileMaker 9 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: [hidden email]
      ICQ: 159333060

--------------------------
Contact us for FileMaker hosting and programming for all versions of  
FileMaker
PHP • CDML • Full email services • Free DNS hosting • Colocation •  
Consulting

On May 27, 2008, at 12:02 AM, Tim 'Webko' Booth wrote:

>> - Is the FM-PHP-API the only one plug in / API supported for  
>> managing FM Databases on the web? (I know can be done with XMl,  
>> XLST without the API and with Lasso (in my case Lasso didn't worked  
>> on my configuration and I could not test it)).
>
> No - I use the FX.php class quite happily, which also plugs in  
> through the XML stream, which has been available since at least FM  
> 5.5 (when did XML become a supported format? Since then...)
>>
>>
>> I Have some clients of small companies that invested on FM5/FM6  
>> Server and that have applications that are running real fine but  
>> would like to do some deployment of information or be able to give  
>> access over the Internet to clients or providers to their process.  
>> For those kind of clients......
>>
>> - The only path to follow is to upgrade ALL to FM9 or above and  
>> move to the PHP-API ? (almost forbidden for the cost of licenses  
>> and the job involved)
>
> No.
>
> If they're on FM5/6, then CDML is still an option (if you can find a  
> copy of FM Unlimited these days...)
>
> FX.php is effectively free and can be used on any XML enabled  
> FileMaker system, although the exact set up will vary quite  
> considerable depending on exactly which versions are being used.
>
> You're not tied to the API, although I would suspect that future  
> releases will have more and more goodies bundled with the API rather  
> than being developed for any other approach/web technology.
>
> Cheers
>
> Webko

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Bob Patin

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Jorge Biquez
Jorge,

Here's a huge consideration: I doubt you'll be able to find anyone  
using anything other than FX.php, FM API, Lasso or CDML these days.  
There were some folks who tried out XSLT back when FileMaker first  
introduced it as a web app solution, but there are very few using it  
now.

The thing to ask yourself is where you'll go for help when you get  
stuck (and you WILL get stuck, especially at first). There are a lot  
of folks using both FX.php and the FileMaker API, and you can get some  
quick assistance as you get familiar with either of these, but if you  
were to try one of the more obscure methods, I can't imagine where  
you'd turn for assistance.

Another thing to keep in mind is that PHP is a robust, popular, mature  
programming environment; there are over 3000 functions written for it,  
and it's present on almost every web server these days. The functions  
come into play all the time for me as I write web apps; before I write  
code to do something new, I usually poke around the web (php.net being  
my favorite source) for functions that do all sorts of useful tricks,  
and invariably I find several to choose from.

My friend Stephen Knight has a book called "FX.php in 8 hours;" I've  
recommended it to others for getting started with FX.php, and yes, you  
actually can learn it in 8 hours. Then, once you're underway,  
subscribe to the FX.php mailing list, where you can get lots of help  
from some good programmers, including Chris Hansen, who wrote FX.php.

You can subscribe to the FX.php list at the following link:

http://www.iviking.org/mailman/listinfo/fx.php_list

My final thought: as someone who has been writing web apps for almost  
10 years, I recommend learning the FileMaker API, only because it's  
the method FileMaker has embraced, and where they are clearly putting  
their efforts. Last year at Devcon I never heard FX.php mentioned  
once, even though it's very popular and a lot of us use it. I  
personally prefer FX, but I recommend the API because it's FileMaker's  
choice...

Best regards,

Bob Patin
Longterm Solutions
[hidden email]
615-333-6858
http://www.longtermsolutions.com
FileMaker 9 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: [hidden email]
      ICQ: 159333060

--------------------------
Contact us for FileMaker hosting and programming for all versions of  
FileMaker
PHP • CDML • Full email services • Free DNS hosting • Colocation •  
Consulting


On May 27, 2008, at 7:53 AM, Jorge Biquez wrote:

> Anyone can comment on these API's based on experience?
>
> They all sound very interesting.
>
> JB

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Dale Bengston

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Jorge Biquez
Hi Jorge,

I will throw in a big enthusiastic plug for FX.php. It works with  
FileMaker 6/7/8/9. It's open source. It requires no additional  
purchase of FMP client seats (sorry FMI). It does, however, require  
proper web-capable server licensing for the version of FileMaker  
you're working with. (For FileMaker 5/6, that means a copy of  
FileMaker Unlimited if you want more than 10 clients to access it in  
an hour's time.)

I encourage you to investigate FX.php yourself. The developer's web  
site is <http://www.iviking.org/FX.php/>. There is a very helpful  
forum/mailing list for FX.php as well - that's how I learned it.

Best regards,

Dale



  --
Dale Bengston
Partner, The Whole Brain Group, LLC
thewholebraingroup.com

On May 27, 2008, at 7:53 AM, Jorge Biquez wrote:

> Hello all.
> At 06:12 a.m. 27/05/2008, you wrote:
>> On May 27, 2008, at 12:51 AM, Jorge Biquez wrote:
>>
>>> Any comments based on your experience with similar projects?
>>
>> A couple...
>>
>> First, APIs:
>>
>> There is a plug-in API available but I'm not aware of any that
>> interact with other programs to the scope you're describing. For FMP
>> 9 there's the XML/XSLT interface, ODBC/JDBC, the PHP API for FMP, and
>> Applescript (I may be forgetting something). Third parties have
>> provided the FX.php API, a VB.Net API, a Ruby API, a Python API, and
>> there are other technologies that leverage the available APIs (such
>> as Lasso).
>
> Anyone can comment on these API's based on experience?
>
> They all sound very interesting.
>
> JB
>
> _______________________________________________
> FMPexperts mailing list
> [hidden email]
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Chris Hansen

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Bob Patin
Jorge,

I'll chime in here...

First off, the 8x speed difference between FX.php and the FileMaker  
API for PHP came from me originally (I think) and it's a bit  
misleading...  Additional testing by myself and others has convinced  
me that this is the result of a performance throttle built into the  
FileMaker API for PHP in the development license of FMS that TechNet  
subscribers receive.  I'm still hoping to test this more, but I don't  
presently have a full license that I can use for testing.  However, I  
haven't seen anyone dispute that FX.php IS notably faster.

Though I am biased towards FX.php, my take has always been examine the  
options and use what works best for you.  Some people find development  
with one tool or another much more to their taste, and after all,  
you're the one who has to live with the tools that you choose =)  And  
since FileMaker's API and FX.php (as well as another open source  
option called FM-and-PHP) are PHP based, much of what you'll need to  
know is shared in common -- a lot of what you'll do is data  
manipulation and display, not just interaction with the database.  I  
spent 5 years with Lasso before I created FX, I was part of a very  
small community group that assisted with the development of  
FileMaker's API, and I still prefer FX... There are those who prefer  
XSLT... Some people swear by Lasso... YMMV...  Try out the options and  
see what you think.

HTH

--Chris Hansen
   FileMaker 8 Certified Developer
   FileMaker 7 Certified Developer
   Creator of FX.php
   "The best way from FileMaker to the Web."
   www.iViking.org

On May 27, 2008, at 8:55 AM, Bob Patin wrote:

> Jorge,
>
> I echo what Tim has said about FX.php; keep in mind that neither the  
> FM API nor FX.php are plugins, per se, but rather a set of PHP  
> libraries that you use to interact with FileMaker's Web Publishing  
> Engine.
>
> I can't imagine considering CDML at this point, although I wrote a  
> lot of sites with it (in fact, Tim was my best source of help when I  
> got stuck). Most FileMaker hosting companies are moving away from  
> hosting CDML sites; we had over 100 databases using CDML at one  
> time, and now we have only 9, mainly because we've migrated most of  
> these to FileMaker 9.
>
> In tests run by other consultants, FX.php came up approximately 8x  
> faster than the FileMaker API; these are not my numbers, as I've  
> never done any testing.
>
> As to which is easier to learn, that's a toss-up; I've been doing FX  
> a lot longer, so I prefer it probably because I'm more proficient  
> with it than with the API, but both achieve the same results, just  
> using a different method. However, once you get familiar with PHP,  
> you can work in both as needed.
>
> As Tim pointed out, unless you want to upgrade to at least FileMaker  
> 7 (which you'd have a hard time finding), FX.php is your only option  
> for PHP interfacing with FileMaker.
>
> Best regards,
>
> Bob Patin
> Longterm Solutions
> [hidden email]
> 615-333-6858
> http://www.longtermsolutions.com
> FileMaker 9 Certified Developer
> Member of FileMaker Business Alliance and FileMaker TechNet
>
>  CONTACT US VIA INSTANT MESSAGING:
>     AIM or iChat: longterm1954
>     Yahoo: longterm_solutions
>     MSN: [hidden email]
>     ICQ: 159333060
>
> --------------------------
> Contact us for FileMaker hosting and programming for all versions of  
> FileMaker
> PHP • CDML • Full email services • Free DNS hosting • Colocation •  
> Consulting
>
> On May 27, 2008, at 12:02 AM, Tim 'Webko' Booth wrote:
>
>>> - Is the FM-PHP-API the only one plug in / API supported for  
>>> managing FM Databases on the web? (I know can be done with XMl,  
>>> XLST without the API and with Lasso (in my case Lasso didn't  
>>> worked on my configuration and I could not test it)).
>>
>> No - I use the FX.php class quite happily, which also plugs in  
>> through the XML stream, which has been available since at least FM  
>> 5.5 (when did XML become a supported format? Since then...)
>>>
>>>
>>> I Have some clients of small companies that invested on FM5/FM6  
>>> Server and that have applications that are running real fine but  
>>> would like to do some deployment of information or be able to give  
>>> access over the Internet to clients or providers to their process.  
>>> For those kind of clients......
>>>
>>> - The only path to follow is to upgrade ALL to FM9 or above and  
>>> move to the PHP-API ? (almost forbidden for the cost of licenses  
>>> and the job involved)
>>
>> No.
>>
>> If they're on FM5/6, then CDML is still an option (if you can find  
>> a copy of FM Unlimited these days...)
>>
>> FX.php is effectively free and can be used on any XML enabled  
>> FileMaker system, although the exact set up will vary quite  
>> considerable depending on exactly which versions are being used.
>>
>> You're not tied to the API, although I would suspect that future  
>> releases will have more and more goodies bundled with the API  
>> rather than being developed for any other approach/web technology.
>>
>> Cheers
>>
>> Webko
>
> _______________________________________________
> FMPexperts mailing list
> [hidden email]
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
>



_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
bfr00

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Bob Patin
> In tests run by other consultants, FX.php came up approximately 8x
> faster than the FileMaker API; these are not my numbers, as I've never
> done any testing.

Wildly wildly inaccurate.

Closer to 8%, not 8X.

"As expected the FileMaker API performance was slightly worse then FX.php,
however not even close to the phenomenal 700% difference claimed by some
critics. Generally the performance difference ranges from 15% to 30%, with
FX.php being faster in all instances."

See http://fmwebschool.com/newsletter/fx_api_benchmarks_v1.pdf

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Bob Patin

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Chris Hansen
Chris,

That's an interesting revelation about the speed difference... since  
90% of what I've written is in FX and not the API, I can't really see  
a difference, but I'm glad that you've told me that before I spread  
inaccuracies... :)

Like Dale (and of course you, the esteemed author of this incredible  
tool), I prefer FX.php; I find it more intuitive, easier to write for,  
and eminently reliable as well.

Another thought just popped into my head about CDML: it's not as  
bulletproof as FX.php. It's not so much that the code fails, because  
that's not the issue; however, CDML requires more server-tending than  
PHP does--PHP requires practically none. There is a memory leak in Web  
Server Connector (this is what CDML uses to talk to FileMaker) that  
will eventually cause a Mac to crash if a site gets a lot of traffic.  
Oddly, it seems to come and go on our servers here; sometimes I've had  
a lot of trouble with it, sometimes not, so I tend to think that it's  
traffic-related.

Also, for CDML, you need to run FileMaker Pro Unlimited 5 or 6, in  
addition to FileMaker Server, which should definitely be used as well;  
on top of that add a web server, and you're involving three machines  
just to host the web app. When you edit a page, you have to upload it  
to both the web server AND the FileMaker Unlimited machine, which  
makes site-updating much more tedious. When using multi-machine  
setups, as we do, this means uploading a single page to 3 or more  
machines each time.

Bob Patin
Longterm Solutions
[hidden email]
615-333-6858
http://www.longtermsolutions.com
FileMaker 9 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: [hidden email]
      ICQ: 159333060

--------------------------
Contact us for FileMaker hosting and programming for all versions of  
FileMaker
PHP • CDML • Full email services • Free DNS hosting • Colocation •  
Consulting

On May 27, 2008, at 10:26 AM, Chris Hansen wrote:

> Jorge,
>
> I'll chime in here...
>
> First off, the 8x speed difference between FX.php and the FileMaker  
> API for PHP came from me originally (I think) and it's a bit  
> misleading...  Additional testing by myself and others has convinced  
> me that this is the result of a performance throttle built into the  
> FileMaker API for PHP in the development license of FMS that TechNet  
> subscribers receive.  I'm still hoping to test this more, but I  
> don't presently have a full license that I can use for testing.  
> However, I haven't seen anyone dispute that FX.php IS notably faster.
>
> Though I am biased towards FX.php, my take has always been examine  
> the options and use what works best for you.  Some people find  
> development with one tool or another much more to their taste, and  
> after all, you're the one who has to live with the tools that you  
> choose =)  And since FileMaker's API and FX.php (as well as another  
> open source option called FM-and-PHP) are PHP based, much of what  
> you'll need to know is shared in common -- a lot of what you'll do  
> is data manipulation and display, not just interaction with the  
> database.  I spent 5 years with Lasso before I created FX, I was  
> part of a very small community group that assisted with the  
> development of FileMaker's API, and I still prefer FX... There are  
> those who prefer XSLT... Some people swear by Lasso... YMMV...  Try  
> out the options and see what you think.
>
> HTH
>
> --Chris Hansen
>  FileMaker 8 Certified Developer
>  FileMaker 7 Certified Developer
>  Creator of FX.php
>  "The best way from FileMaker to the Web."
>  www.iViking.org
>
> On May 27, 2008, at 8:55 AM, Bob Patin wrote:
>> Jorge,
>>
>> I echo what Tim has said about FX.php; keep in mind that neither  
>> the FM API nor FX.php are plugins, per se, but rather a set of PHP  
>> libraries that you use to interact with FileMaker's Web Publishing  
>> Engine.
>>
>> I can't imagine considering CDML at this point, although I wrote a  
>> lot of sites with it (in fact, Tim was my best source of help when  
>> I got stuck). Most FileMaker hosting companies are moving away from  
>> hosting CDML sites; we had over 100 databases using CDML at one  
>> time, and now we have only 9, mainly because we've migrated most of  
>> these to FileMaker 9.
>>
>> In tests run by other consultants, FX.php came up approximately 8x  
>> faster than the FileMaker API; these are not my numbers, as I've  
>> never done any testing.
>>
>> As to which is easier to learn, that's a toss-up; I've been doing  
>> FX a lot longer, so I prefer it probably because I'm more  
>> proficient with it than with the API, but both achieve the same  
>> results, just using a different method. However, once you get  
>> familiar with PHP, you can work in both as needed.
>>
>> As Tim pointed out, unless you want to upgrade to at least  
>> FileMaker 7 (which you'd have a hard time finding), FX.php is your  
>> only option for PHP interfacing with FileMaker.
>>
>> Best regards,
>>
>> Bob Patin
>> Longterm Solutions
>> [hidden email]
>> 615-333-6858
>> http://www.longtermsolutions.com
>> FileMaker 9 Certified Developer
>> Member of FileMaker Business Alliance and FileMaker TechNet
>>
>> CONTACT US VIA INSTANT MESSAGING:
>>    AIM or iChat: longterm1954
>>    Yahoo: longterm_solutions
>>    MSN: [hidden email]
>>    ICQ: 159333060
>>
>> --------------------------
>> Contact us for FileMaker hosting and programming for all versions  
>> of FileMaker
>> PHP • CDML • Full email services • Free DNS hosting • Colocation •  
>> Consulting
>>
>> On May 27, 2008, at 12:02 AM, Tim 'Webko' Booth wrote:
>>
>>>> - Is the FM-PHP-API the only one plug in / API supported for  
>>>> managing FM Databases on the web? (I know can be done with XMl,  
>>>> XLST without the API and with Lasso (in my case Lasso didn't  
>>>> worked on my configuration and I could not test it)).
>>>
>>> No - I use the FX.php class quite happily, which also plugs in  
>>> through the XML stream, which has been available since at least FM  
>>> 5.5 (when did XML become a supported format? Since then...)
>>>>
>>>>
>>>> I Have some clients of small companies that invested on FM5/FM6  
>>>> Server and that have applications that are running real fine but  
>>>> would like to do some deployment of information or be able to  
>>>> give access over the Internet to clients or providers to their  
>>>> process. For those kind of clients......
>>>>
>>>> - The only path to follow is to upgrade ALL to FM9 or above and  
>>>> move to the PHP-API ? (almost forbidden for the cost of licenses  
>>>> and the job involved)
>>>
>>> No.
>>>
>>> If they're on FM5/6, then CDML is still an option (if you can find  
>>> a copy of FM Unlimited these days...)
>>>
>>> FX.php is effectively free and can be used on any XML enabled  
>>> FileMaker system, although the exact set up will vary quite  
>>> considerable depending on exactly which versions are being used.
>>>
>>> You're not tied to the API, although I would suspect that future  
>>> releases will have more and more goodies bundled with the API  
>>> rather than being developed for any other approach/web technology.
>>>
>>> Cheers
>>>
>>> Webko
>>
>> _______________________________________________
>> FMPexperts mailing list
>> [hidden email]
>> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
>>
>
>
>
> _______________________________________________
> FMPexperts mailing list
> [hidden email]
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Bob Patin

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by bfr00
Yes, but to my knowledge, those tests have never been confirmed. In  
fact, one of my friends (who's on this list) wanted me to run a  
similar test, which I never got around to... (sorry about that!).

I was only quoted what I had been told, but I will point out that both  
of the testers (Chris was one, as he said) were testing in their own  
environments. Stephen tested on his machines, and I can't help but  
wonder if I were to test on my servers, if I'd get a different outcome  
as well.

 From my perspective, this is irrelevant anyway; FMI has clearly put  
their support behind their own API, much to the disappointment of many  
of FX users. At Devcon last summer, many of us FX programmers got  
together in an off-the-schedule meet-up, and it was gratifying to see  
how many people showed up, even though FX wasn't being mentioned by FMI.

What was clear to me was how much effort FMI is putting into the API,  
with their PHP Site Assistant and with FMS 9. I don't care for the  
hassle involved in setting up FMS 9 to work with a web server; it was  
much easier in FMSA 8 to merely install the server, install WPE, and  
then configure WPE for a particular web server. However, if FMS 9  
doesn't see your web server, you have to re-install WPE (the only  
method I've found to get around the problem) in order to "force" FMS 9  
to see your web server. I wasted several hours with this one night.

As Chris pointed out, the techniques are essentially the same; with a  
web app, you're creating, finding, editing or deleting records, and  
then manipulating the data for display on the web. The manipulation of  
the data is where the real skills come into play; write a bad web app  
and the data looks awful and is difficult to use; write an elegant web  
app and you can present a really clean interface for users. This is  
where a good knowledge of PHP comes in to play, rather than the choice  
of the interface.

Bob Patin
Longterm Solutions
[hidden email]
615-333-6858
http://www.longtermsolutions.com
FileMaker 9 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: [hidden email]
      ICQ: 159333060

--------------------------
Contact us for FileMaker hosting and programming for all versions of  
FileMaker
PHP • CDML • Full email services • Free DNS hosting • Colocation •  
Consulting

On May 27, 2008, at 10:35 AM, Bruce Robertson wrote:

>> In tests run by other consultants, FX.php came up approximately 8x
>> faster than the FileMaker API; these are not my numbers, as I've  
>> never
>> done any testing.
>
> Wildly wildly inaccurate.
>
> Closer to 8%, not 8X.
>
> "As expected the FileMaker API performance was slightly worse then  
> FX.php,
> however not even close to the phenomenal 700% difference claimed by  
> some
> critics. Generally the performance difference ranges from 15% to  
> 30%, with
> FX.php being faster in all instances."
>
> See http://fmwebschool.com/newsletter/fx_api_benchmarks_v1.pdf
>
> _______________________________________________
> FMPexperts mailing list
> [hidden email]
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Beverly Voth-2

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
On 05/27/08 11:54 AM, "Bob Patin" <[hidden email]> wrote in whole or in part:

> As Chris pointed out, the techniques are essentially the same; with a
> web app, you're creating, finding, editing or deleting records, and
> then manipulating the data for display on the web. The manipulation of
> the data is where the real skills come into play; write a bad web app
> and the data looks awful and is difficult to use; write an elegant web
> app and you can present a really clean interface for users. This is
> where a good knowledge of PHP comes in to play, rather than the choice
> of the interface.

Yes, and I wonder if the "easy-of-use" is the reason people use one
interface or another. Look at the people that jumped on the CDML bandwagon!
You have to admit that the Site Assistant is an attractive lure, just as
Home Page was.

I praise this as well-and-good. I just know that there was/is a lot of great
stuff that is NOT being done with web sites (and the databases behind them)
that result from going the easy route. And as a result these sites really
are slow old dogs.

It might be difficult to discern if the "problem" is the api or the
design...

:)
--
Beverly Voth                       Tier3 Data & Web Services Group, LLC
606-864-0041                            http://www.tier3web.com/xml.htm

               Web Design & Hosting * Apple: ACN & ADC
   Certified FileMaker 7 & 9 Developer * FileMaker Business Alliance
    Coldfusion, Witango, PHP, MS SQL, MySQL, FMP, XML/XSLT, CSS
   Over 14 years experience integrating databases and the internet!


_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Mike Duncan-2

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Bob Patin
Although I've run into the same "wasted several hours" figuring out the
deployment and getting the server to see the web publishing engine, I
haven't had trouble doing more recent installs. And I like the ability
to manage an entire deployment with FMS 9's admin tools (when they work)
rather than previous versions.

In all fairness, I had probably just as much headache caused trying to
get web publishing engines to magically "appear" to FM server in 7 and 8
as I have in 9, and then having two completely different methods of
controlling each component was a little less than intuitive. I certainly
wish for more stability in the current version, regardless what API
you're connecting with.

Also, just to throw in my opinion, but some people miss the point with
php development. It's really only half the picture, since you still can
output a complex interface with html/css/dhtml/ajax (and more!) I've
seen instances where the php code is brilliant, but the resulting site
looks less than appealing in a browser. That gives you plenty to keep
busy in producing nice web apps :)

Bob Patin wrote:

> What was clear to me was how much effort FMI is putting into the API,
> with their PHP Site Assistant and with FMS 9. I don't care for the
> hassle involved in setting up FMS 9 to work with a web server; it was
> much easier in FMSA 8 to merely install the server, install WPE, and
> then configure WPE for a particular web server. However, if FMS 9
> doesn't see your web server, you have to re-install WPE (the only
> method I've found to get around the problem) in order to "force" FMS 9
> to see your web server. I wasted several hours with this one night.
>
> As Chris pointed out, the techniques are essentially the same; with a
> web app, you're creating, finding, editing or deleting records, and
> then manipulating the data for display on the web. The manipulation of
> the data is where the real skills come into play; write a bad web app
> and the data looks awful and is difficult to use; write an elegant web
> app and you can present a really clean interface for users. This is
> where a good knowledge of PHP comes in to play, rather than the choice
> of the interface.

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Bob Patin

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by Beverly Voth-2
Good point, Bev; when I looked at the code generated by the API, I was  
amazed at the load of stuff that gets written. If I were to write the  
same site using the API, I would probably use less than half the  
amount of code that the API generates with Site Assistant.

While I think it's a useful tool for some folks, just as IWP is, I use  
neither technology, because of the limitations with both. IWP is great  
in local networks, and for low-traffic situations, but I never  
recommend it to my clients. Site Assistant, while fairly easy to use,  
presents a similar scenario; originally I'd thought that I'd learn the  
API by generating a few sites using Site Assistant and then  
dismantling the code, but I quickly saw that the Site-Assistant-
generated code wasn't going to present the easiest way to learn the API.

I think it's the same scenario that comes up when someone generates a  
site using FMWebSchool's FM Studio; it's easy to generate a site using  
it, but then to go in and tweak the code you have to deal with a lot  
more code just to make simple changes. For me, it's far easier to  
simply write the site, putting in only the code that is needed for  
that specific site, rather than dealing with a lot of functions that  
aren't being used.

Bob Patin
Longterm Solutions
[hidden email]
615-333-6858
http://www.longtermsolutions.com
FileMaker 9 Certified Developer
Member of FileMaker Business Alliance and FileMaker TechNet

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: [hidden email]
      ICQ: 159333060

--------------------------
Contact us for FileMaker hosting and programming for all versions of  
FileMaker
PHP • CDML • Full email services • Free DNS hosting • Colocation •  
Consulting



On May 27, 2008, at 11:12 AM, Beverly Voth wrote:

> Yes, and I wonder if the "easy-of-use" is the reason people use one
> interface or another. Look at the people that jumped on the CDML  
> bandwagon!
> You have to admit that the Site Assistant is an attractive lure,  
> just as
> Home Page was.
>
> I praise this as well-and-good. I just know that there was/is a lot  
> of great
> stuff that is NOT being done with web sites (and the databases  
> behind them)
> that result from going the easy route. And as a result these sites  
> really
> are slow old dogs.
>
> It might be difficult to discern if the "problem" is the api or the
> design...

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Dale Bengston

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
In reply to this post by bfr00
Bruce,

As far as I know, there are two completely different tests being  
compared here: one by Chris Hansen and one by FMWebSchool. The tests  
used different hardware platforms, different test databases and  
different PHP files. The only thing consistent was that both tests  
reported FX.php was faster. As to how much, who really knows?

I have both sets of test files, but do not have FMS9 deployed anywhere  
to run the PHP API; if anyone cares to test these head-to-head, let me  
know and I'll send you the files.

Dale


On May 27, 2008, at 10:35 AM, Bruce Robertson wrote:

>> In tests run by other consultants, FX.php came up approximately 8x
>> faster than the FileMaker API; these are not my numbers, as I've  
>> never
>> done any testing.
>
> Wildly wildly inaccurate.
>
> Closer to 8%, not 8X.
>
> "As expected the FileMaker API performance was slightly worse then  
> FX.php,
> however not even close to the phenomenal 700% difference claimed by  
> some
> critics. Generally the performance difference ranges from 15% to  
> 30%, with
> FX.php being faster in all instances."
>
> See http://fmwebschool.com/newsletter/fx_api_benchmarks_v1.pdf
>
> _______________________________________________
> FMPexperts mailing list
> [hidden email]
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
Chris Hansen

Re: FM-PHP-API The only API/Plug in available?

Reply Threaded More More options
Print post
Permalink
Also, as I noted, my tests were performed using the TechNet Dev  
license of FMS.  I strongly suspect the FMWebschool tests were  
performed using a regular FMS license.  I think it would be useful to  
developers to know _if_ and _how_much_ throttling occurs in that  
environment.

--Chris

On May 27, 2008, at 10:43 AM, Dale Bengston wrote:

> Bruce,
>
> As far as I know, there are two completely different tests being  
> compared here: one by Chris Hansen and one by FMWebSchool. The tests  
> used different hardware platforms, different test databases and  
> different PHP files. The only thing consistent was that both tests  
> reported FX.php was faster. As to how much, who really knows?
>
> I have both sets of test files, but do not have FMS9 deployed  
> anywhere to run the PHP API; if anyone cares to test these head-to-
> head, let me know and I'll send you the files.
>
> Dale
>
>
> On May 27, 2008, at 10:35 AM, Bruce Robertson wrote:
>
>>> In tests run by other consultants, FX.php came up approximately 8x
>>> faster than the FileMaker API; these are not my numbers, as I've  
>>> never
>>> done any testing.
>>
>> Wildly wildly inaccurate.
>>
>> Closer to 8%, not 8X.
>>
>> "As expected the FileMaker API performance was slightly worse then  
>> FX.php,
>> however not even close to the phenomenal 700% difference claimed by  
>> some
>> critics. Generally the performance difference ranges from 15% to  
>> 30%, with
>> FX.php being faster in all instances."
>>
>> See http://fmwebschool.com/newsletter/fx_api_benchmarks_v1.pdf
>>
>> _______________________________________________
>> FMPexperts mailing list
>> [hidden email]
>> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
>
> _______________________________________________
> FMPexperts mailing list
> [hidden email]
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
>

_______________________________________________
FMPexperts mailing list
[hidden email]
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au
1 2