The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I mean... you can literally just do a google for it if you really wanted to answer that question yourself. Rob Pike has mentioned it in talks, Stephen Cleary mentions it in Concurrency in C# iirc, Joseph Albahari recognizes the distinction in Threading in C# by referring to parallelism as "genuine concurrency" implying a subset, etc. Even the wiki you linked to agrees that concurrency is a more general term that can involve things such as time-slicing, asynchronicity (yielding time-slices), and parallelism.
I do see the flaw in my statement now though. While parallelism I think is the worst offender by far and general time-slicing the least offender due to time-slices being relatively long - it is still possible to run into issues.
If you had addressed my initial question this would be a relevant reply. However, you explicitly went after my references which are easily validated via Google. Also my initial question is not easily solved via Google as time-slicing (a subset of concurrency) is only relevant if data-sharing between processes is taking place. This is not as trivial as it would initially seem as processes have their own address-space
Yes, that is a good feeling. Especially when hard work was involved.
Since you seem to be the resident expert on low-level programming, I wonder if I might prevail upon you to take a look at a question I posted on the Architecture board. If you have any insight into it, I would definitely appreciate your words of wisdom.
The difficult we do right away...
...the impossible takes slightly longer.
What about an article or a tip to explain what you found out before you forget?
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
It might be at first, then you start feeling kinda surprised, then you start thinking something bad has to happen at some point, then self-doubt sets in and you can't shake off that feeling of unease and you can't help but go and spend a couple of hours double-checking all of the code, looking for that ever-so-subtle bug you might have missed...and you can't find it.
I'd rather have something almost work, find a problem, do a quick fix, then confirm it's all good. It's like I have to justify my pessimism.
I have 2 servers running SQL Server 2014 which are in different location. Server 1 does not see Server 2 and vice versa. I have a shared drive where both servers can access. On server 1, I have created a backup job and the backup file is saved locally. I need to move the backup to the shared drive. And then, on Server 2, take the backup file and restore it. I need to automate the process.