I think I know the answer to this one but I though it worth asking.
I am working on a graphing / reporting module in another language (REALBasic) that will probably run on the same machine as Lasso. It will grab raw data and create graphs, PDFs, etc.
So, I have two ways for Lasso and my app to interact. My app could communication with Lasso through Apache for updates, to get raw data, etc. I already have this working for some other functions.
OR Lasso could write the "raw" data to a file on disk and then pass the reference to my app when it comes looking for work (or gets called in other ways).
It seems that, for larger data sets, popping out a file would be faster than streaming things out through Apache and the network stack....
any opinions about which one might be faster and what other pitfalls may exist?
regards,
Steve
--
--
This list is a free service of LassoSoft:
http://www.LassoSoft.com/Search the list archives:
http://www.ListSearch.com/Lasso/Browse/Manage your subscription:
http://www.ListSearch.com/Lasso/