filewatch | Single header folder/file watcher | File Utils library

I implemented a Revit add-in in C# to import a LandXML surface to a TopographySurface. The LAS file format is just as simple and readable as LandXML, so that ought to give you what you need. I am interested in implementing such a thing for myself as well, in fact, so maybe if you can share a simple LAZ sample file or two I can take a look at it as well. Thank you.

I see that decap.exe is an Autodesk product, and has nothing to do with Python. What exactly are you trying to achieve? Just generate the topography surface, or something else besides that?

Yes, you'll need to restart the server on changes. You can use a file watcher to do this automatically. PHP doesn't provide a hotreload feature currently.

You can't use cooperative multitasking without a scheduler / event loop, no.

I can't tell you why you're seeing the behaviour you're observing. I can reproduce the error with SBT 1.3.13. When I use SBT 1.4.9 the custom task only runs once as you would expect.

In the Task Scheduler you can start the script with with: powershell.exe -windowstyle hidden -File "path to script" There you can also make a trigger, that it should be executed at logon. In each Task there is an option, that the task ends after a specific amount of time. You can disable that.

extern a class member is not allowed, If we can do that, for instances of a class type, compiler don't know which address to resolve while linking. you can do like this:

Do not use backslash in the path option, it is treated as an escape, so logstash is waiting for the file "E:ferdowsi-datadatalogslogs" to be created. Use forward slash or double backslash.

Need to configure the service to depend on winmgmt by opening the cmd prompt

sc config "NAME_OF_YOUR_SERVICE" depend= winmgmt I found answer here

The general question:

Microservices - should there be multiple instances of the same service?

It depends why you are considering using them, and what the alternatives are. For example, you could have multiple instances for redundancy, or because a single instance on a single machine doesn't have the capacity. Or you could run multiple instances because the service and/or service stack is single threaded.

But running multiple instances of a microservice could breaks things if the service is not designed with this in mind. Obviously, in that case you shouldn't do it.

Note: If microservice is (truly) stateless, then replicating it is less likely to break things from a "functional" perspective. But this is hardly a useful observation, since there can still be ways that it could break things "operationally"; e.g. due to consuming resources ...

In short, you need to understand the context to decide whether you should or should not replicate a service.

An example:

Here if multiple instance of filewatcher service running on different server (logical or physical server) and fetching file from same location than it will create the duplicate records.

That could be a scenario where you don't run multiple instances because it breaks things. (What would you be achieving with multiple file watchers watching the same location?)

Alternatively you could implement the file watcher instances to de-dup the records as they put them into the database (assuming that you are using a database). Or you could deal with the duplicate records later.

Either approach could be correct. It depends on the context.

Bottom line: I cannot think of any general architectural principles, techniques or advice, apart from the obvious advice that you need to understand the context, and decide what to do based on that.

Note: There are no Best Practices