[Dataperf] DP Web Server

Tim Rude timrude at hotmail.com
Thu Aug 3 21:04:47 CEST 2017


Not really a need for DP to monitor constantly. The importing of files can be done by DP with a command line already. If real-time monitoring is needed, something could be created using a third party tool (like AutoIt, Visual Basic, or many other languages) to monitor for new files and then run the DP command line to import them as needed.

I don't know how much Lew would be interested in (or able to) making further changes to DP. Haven't heard from him in some time.

Tim Rude

On 8/3/2017 1:43 PM, Chris Pedersen wrote:
All  WP products had the ability to run from the WPshell, and exchange data via the clipboard
Data Perfect has these abilities, via the import field and import record commands.

These functions iirc were implimented via temporary files  Ie, when you copied text to the clipboard it created a file ~1234567.tmp.

---------------------------

Second subject:

People have used dp to drive web sites.  More or less, they run dp in a loop.  Load dp importing a transaction file, exit dp, go back into the loop.

If Lew could be interested,   I would propose the following:
\TransIn Directory under dp.
\TransOut Directory under dp.

Have dp constantly monitor the TransIn directory for transaction logs.  If a file is found, import it as per a standard dp transaction log

Secondly, have one new on record edit option.   On edit/save run a report.  This would be like any other report generated from the menu or report list.   The user would be expected to put it in the \TransOut directory.

This ability to import and export files real time, is really all thats necessary to turn DP into a stable, robust webserver.





_______________________________________________
Dataperf mailing list
Dataperf at dataperfect.nl<mailto:Dataperf at dataperfect.nl>
http://lists.dataperfect.nl/cgi-bin/mailman/listinfo/dataperf


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dataperfect.nl/pipermail/dataperf/attachments/20170803/8f00cd1a/attachment.html>


More information about the Dataperf mailing list