As I'm overhauling stuff here, I'm wondering what the best strategy for
calling methods is.
Are there any performance gains/losses by calling "web" methods through
Active4D libraries instead of calling them through 4D? This would
mostly be for utility-type methods that formatted, cleaned up or
validated stuff.
My thinking is to keep "web" methods separate so that other users don't
accidentally change methods/parameters that web pages would use, even
though many of them are repeated and appear in the 4D structure. Also,
I like the idea of everything web-related being in one place.
On the other hand, If it's more efficient to call through 4D, I could
always consider creating them in 4D, but just prefix the methods with
some unique identifier.
Something else to keep in mind ... I'm currently doing this in 6.7 and
Active4D v3 for compatibility reasons at the moment. When we go up to
Acitve4D v4 and 4D2004, would the same apply? Would conversion to a
Fusebox site be easier this way?
Your opinions are appreciated.
Darin
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
