Richard, A direct SQL query followed by a FTP command to check existence, on a per file basis takes about 150 millisecs. The same query performed by LC Server, and FTP existence check, takes about 500 millisecs.
I understand that sockets would be more efficient for high volume io. At most, my list of filenames would be under 300 lines at a time. In an earlier post, a few weeks back, you mentioned that you had achieved high efficiency using text files and arrays with server. That may not be relevant to this, but it made me consider simply ftp-ing my list, followed by a http request to tell the server there's a new task, and have it return the original list, plus y/n for the existence check. I'm not really fond of the idea of writing the list to the drive just for processing. I doubt that all of the data (the list) could be carried in a GET parameter of the URL. I don't know the URL length limitations, or if there is a limit. ~Roger On Wed, Aug 28, 2013 at 9:34 AM, Richard Gaskin <ambassa...@fourthworld.com>wrote: > Roger Eller wrote: > >> Additionally, I want to pass a list to be queried and verified, instead of >> one line at a time, passing parameters with GET. Any recommendations on >> that front? >> > > For reasons I can't understand, though the LC Server engine is 50% larger > than a GUI Linux standalone, I believe it includes no socket support (I > hope I'm mistaken on that - anyone have newer info?). > > If socket communication is critical you may consider using a standalone > instead. > > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
