intriguing the result is:
Did Microsoft dropped support for ActiveXObjects? Is this real life? Then miraculously when you call:
you do actually get:
You just miraculously created an undefined object. Good job!
Fascinating implementation indeed.
If you want to edit your Joomla or Wordpress article. and you want to insert a programming code sample, you can do that by the click of a button with Ciplogic's CodeEditor. The good thing now is that you can also add PowerShell into your article, this being the new programming language added in version 1.2.
Here is a sample on how it looks for a random script from the Internet:
So in order to start, let's build first an utility class that we'll use in several places, the onceMany utility function:
As you can see at line 3, we will keep everything in the ciplogic namespace. From this moment on, we can call:
And we don't need to keep a new array for join operations.
Here is a quick overview, in case you don't know much about them:
Let me translate this for you: Worker threads are a pain to even package in their own files, you can't call something like:
No, that would be too easy, since from that method I could be able to access shared state, so let's make it awkward and weird, why not:
and from the new file call:
All the libraries, that you use both in your worker, or in your main code? Better load them twice.
But wait, there's more!
There is a new object visible named self, that is the worker reference (if it's a script inside a window, self == window).
So let's say you would want to process async a bunch of data, whenever it's being sent from the parent - again, there is no shared context, well why not go with:
Looks simple, isn't it? Except it's in a different bloody file, and did I mentioned that breakpoints in the worker thread code don't stop?
So I was checking how's the bruteforce going on my website:
My hosting has shorewall (or some form of it), that automatically bans people who have too many atempts, and my config has for sshd: