In the captureEventLog() and handleLoadProfileActions() functions of the server example 2, the capture action of the profile generic is reading each time all the saving data in the file then append the new data to the file then write all the data again including the new one instead of appending directly the new data to the file at the correct row index.
Is it any specific explanation to that way of capturing? Can we instead seeking to the specific row index and write directly the new data or there any problem?
The reason why all the data is read and then saved to the file is that direct writing was causing problems with some PCs. This approach is more effective in different environments. You can try direct writing.
Hi,
Hi,
The reason why all the data is read and then saved to the file is that direct writing was causing problems with some PCs. This approach is more effective in different environments. You can try direct writing.
BR,
Mikko
Hi,
Hi,
We are trying the direct writing and it seems to work just fine.
Thank you.
Best Regards,
Lara Wakim