Hmm, it’s been a few days of reflection. I don’t think I expected my post on the bugs we were fixing in Update 2.1 to generate so many comments about other bugs that people are hitting. Let me share some questions that have been on my mind and my thoughts on them… Why did I... Read more
Updated versions of Facebook, Facebook Messenger and Instagram are rolling out for various Windows 10 devices.
A New Chapter In Library Technology | EBSCO post
A recent article by Marshall Breeding describes a new open source
project introducing a new chapter in library technology: a first-ever
community collaboration to develop a modern open source library services
platform with full ILS functionality. The project is well underway with
major support from EBSCO, technology development led by Index Data
I have written extensively about the blittable format already, so I’ll not get into that again. But what I wanted to do in this post is to discuss the implication of the intersection of two very important features: The blittable format requires no further action to be useful. Voron is based on a memory mapped file concept. Those two, brought together, are quite interesting. To see why, let us consider the current state of affairs. In RavenDB 3.0, we store the data as json directly. Whenever we need to read a document, we need to load the document from disk, parse the json,
load it into .NET objects, and only then do something with it. When we just got started with RavenDB, it didn’t actually matter to us. Our main concern was I/O, and that dominated all our costs. We spent multiple releases improving on that, and the solution was the prefetcher. Prefetcher will load documents from the disk and make them ready to be indexed. The prefetcher is running concurrently to indexing, so we can parallelize I/O and CPU work. That allow us to reduce most of the I/O wait times, but it still left us with problems. If two indexes are working, and they...(Read whole news on source site)
In this article, Marcin Policht describes the basic functionality and implementation steps for Azure SQL Database's Elastic Database jobs.
Learn how to use Biml to create a SSIS-package with a Script component that can read from Twitter.
Information A look at ES6 Maps – Jaime González García shares a look at the Map data structure in ECMAScript 2015, sharing examples of its use in a number of scenarios News from Xamarin Evolve: What’s next for Visual Studio and Xamarin – Amanda Silver shares the latest news on the work integrating Xamarin into […]
We have a Message Bus application where messages are passed all around, from one application instance to another. This message traffic can be intranet, inter-domain or internet. We keep the messages safe from prying eyes by using RSA encryption (public keys are stored in databases). Now, the whole RSA encryption thing is a topic for another day (or just Google for more info, in case I never get around to writing that blog post). Today, I’m going to talk about what to do if you need to move one of your existing Message Bus deployments to another computer for some
reason (like the computer is old or dying and you need to replace it with new hardware). This new computer will not have your RSA KeyContainer. Creating a new KeyContainer with the same name doesn’t get you the same keys, obviously. All your messaging traffic comes to a screeching halt, because now the messages can’t be decrypted with these different keys.The solution is to copy your RSA KeyContainer to the new computer. I have a little utility application that I wrote that will read the RSA KeyContainer and write it to an XML file. The utility will also read from...(Read whole news on source site)