[FX.php List] Best Practice

[Gjermund Gusland Thorsen]

Affirmative

On 9/20/06, Alex Gates <alex at gandrpublishing.com> wrote:
> Yes, I think it does - as a returned query puts everything from the
> layout in the resulting array.
>
> Please correct me if I'm wrong...
>
> Alex P. Gates
>
> -----Original Message-----
> From: fx.php_list-bounces at mail.iviking.org
> [mailto:fx.php_list-bounces at mail.iviking.org] On Behalf Of Tom Sepper
> Sent: Wednesday, September 20, 2006 12:46 PM
> To: FX.php Discussion List
> Subject: [FX.php List] Best Practice
>
> Not to hijack this, but ggt got me thinking.
>
> Since any field to be used with FX.php has to be on the layout specified
> in the FX instance, that begs the question..  Does placing all fields a
> table on the layout slow down the FX.php >> WPE/XML >> FM query?
>
> ---
> Tom Sepper
> Director of Information Technology
> Director's Choice Tour & Travel
>
> P 806.762.6354
> F 806.763.7637
>
> tsepper at dctandt.com
> www.directorschoicetourandtravel.com
>
> -----Original Message-----
> From: fx.php_list-bounces at mail.iviking.org
> [mailto:fx.php_list-bounces at mail.iviking.org] On Behalf Of Gjermund
> Gusland Thorsen
> Sent: Wednesday, September 20, 2006 12:41 PM
> To: FX.php Discussion List
> Subject: Re: Re: [FX.php List] Anyone using XSLT anymore?
>
> Hmm sounds like your client only needs one field pr layout.
>
> See if that improves speed, to me the solution sounds silly...
>
> There are template engines like smarty, or you could just make a
> couple of php/html templates yourself...
>
> ggt667
>
> On 9/20/06, Bob Patin <bob at patin.com> wrote:
> >
> > I'm using 8.5... but what I'm thinking is that I'll just add a field
> to the
> > layout that has the URL to the HTML file... shouldn't add any
> overhead, I
> > woudln't think, since all I'm returning from FileMaker is the URL.
> >
> > I may still return some of the HTML from the database; these reports
> are
> > made up of about 20 chunks of HTML, and when I return the chunks the
> speed
> > is just fine. The problem arises when I have to return all 20 "chunks"
> in
> > one long report; I may just output the long report to static HTML and
> leave
> > the little chunks embedded in the database...
> >
> > At any rate, it's great to see a solution. I'd completely overlooked
> the
> > possibility of using a hybrid of static HTML and database... I use it
> all
> > the time for photos and such, but hadn't thought about it in this
> > context...
> >
> > Best,
> >
> > Bob Patin
> > Longterm Solutions
> > bob at longtermsolutions.com
> > 615-333-6858
> > http://www.longtermsolutions.com
> >
> >   CONTACT US VIA INSTANT MESSAGING:
> >      AIM or iChat: longterm1954
> >      Yahoo: longterm_solutions
> >      MSN: tech at longtermsolutions.com
> >      ICQ: 159333060
> >
> >
> >
> >
> > On Sep 20, 2006, at 11:04 AM, DC wrote:
> > I just remembered that in order for this architectural change to work
> you
> > must be using a version of the WPE that lets you return the data from
> a
> > layout that is different from your search layout. otherwise there is
> no way
> > to stop the HTML field that you want to search from spewing itself
> into the
> > XML result. so, this scheme wouldn't work in FMP6.
> >
> > dan
> >
> >
> > _______________________________________________
> > FX.php_List mailing list
> > FX.php_List at mail.iviking.org
> > http://www.iviking.org/mailman/listinfo/fx.php_list
> >
> >
> >
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>
>
>
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>