Apache server status for venomous.86it.us

Server Version: Apache/2.4.27 (Unix) OpenSSL/1.0.1e-fips mod_bwlimited/1.4
Server MPM: prefork
Server Built: Oct 13 2017 09:14:05 pm

I just upgraded Rack 68, the main network server. We are now running MariaDB Version: 10.1.28 globally... We were running MySQL Version: 5.6 and using the Federated engine. It turns out that the Federated project was dropped and at one time that portion of the code was maintained by a few Oracle developers. This is no longer the case and now with MariaDB, since the federated engine project was dropped, there definitely needed to be something done about it. A wonderful idea came about and it was to keep the project alive and get some fresh souls working on it. I give you FederatedX which is taking the place of the old not very well maintained Federated engine and with fresh souls helping the engine progress. They have already done some new wonderful things... 

What is the FederatedX storage engine?

The FederatedX Storage Engine is a storage engine that works with both MariaDB and MySQL. Where other storage engines are built as interfaces to lower-level file-based data stores, FederatedX uses libmysql to talk to the data source, the data source being a remote RDBMS. Currently, since FederatedX only uses libmysql, it can only talk to another MySQL RDBMS. The plan is, of course, to be able to use other RDBMS systems as a data source. There is an existing project Federated ODBC which was able to use PostgreSQL as a remote data source, and it is this type of functionality which will be brought to FederatedX in subsequent versions.

History

The history of FederatedX is derived from the History of Federated. Cisco needed a MySQL storage engine that would allow them to consolidate remote tables on some sort of routing device, being able to interact with these remote tables as if they were local to the device, but not actually on the device, since the routing device had only so much storage space. The first prototype of the Federated Storage Engine was developed by JD (need to check on this- Brian Aker can verify) using the HANDLER interface. Brian handed the code to Patrick Galbraith and explained how it needed to work, and with Brian and Monty's tutelage and Patrick had a working Federated Storage Engine with MySQL 5.0. Eventually, Federated was released to the public in the MySQL 5.0 release. There is every indication that the Federated engine existed in previous versions of MySQL due to the fact that Ernest Allen Buffington had previously used it with PHP-Nuke Titanium early on through discoveries of his own and with little or no documentation.

We were not quite ready to upgrade all the way to MariaDB 10.0.2 but when we did FederatedX had new support for assisted table discovery. So there is that and the fact that new exciting things are happening with the new engine project. It looks like the fresh new souls are working their buns off to make it awesome and are going the extra miles needed.

Internal workings of FederatedX

Normal database files are local and as such: You create a table called 'users', a file such as 'users.MYD' is created. A handler reads, inserts, deletes, updates data in this file. The data is stored in particular format, so to read, that data has to be parsed into fields, to write, fields have to be stored in this format to write to this data file.

With the FederatedX storage engine, there will be no local files for each table's data (such as .MYD). A foreign database will store the data that would normally be in this file. This will necessitate the use of the MySQL client API to read, delete, update, insert this data. The data will have to be retrieved via an SQL call "SELECT * FROM users ". Then, to read this data, it will have to be retrieved via mysql_fetch_row
one row at a time and then converted from the column in the select into the format that the handler expects.

The basic functionality of how FederatedX works

• The user issues an SQL statement against the local federatedX table. This statement is parsed into an item tree
• FederatedX uses the MySQL handler API to implement the various methods required for the storage engine.
• It has access to the item tree for the SQL statement issued, as well as the Table object and each of its Field members. 
• With this information, FederatedX constructs an SQL statement
• The constructed SQL statement is sent to the Foreign data source through libmysql using the MySQL client API
• The Foreign database reads the SQL statement and sends the result back to the MySQL client API to the origin
• If the original SQL statement has a result set from the Foreign data source, the FederatedX storage engine iterates
• through the result set and converts each row and column to the internal handler format
• If the original SQL statement only returns the number of rows returned (affected_rows), that number is added to the
• table stats which results in the user seeing how many rows were affected.

Does Microsoft make Internet Explorer purposely not adhere well to standards?

Some people just do not get it and think that it is the other way around says Nick Malik who once worked at Microsoft but was fired. He thinks very poorly when it comes to logic as does a lot of other people out there that are severely wet behind the ears when it comes to rolling in new and better technology and/or standards while at the same time still trying support many useless standards developed in the past by Microsoft and other 3rd party want to be browser developers.

HTML 5 is here to stay and so is a lot of the XHTML 1.0 standards that already exist. Nick went on to say that he realizes that some standards came from Microsoft and that he thinks they did a fine job of implementing them and that invalidates the logic of programmers old enough to be his grandfather. 

He went on to say that IE is a bloated, IMHO. It supports technologies that were widely used in business, but rarely used on the open internet, like ActiveX. New browsers don't offer backward compatibility and are therefore easier to write to the new standards. He then asked me "So, what's the solution? A new, lightweight browser from Microsoft?"

My reply was simple, I told him that Microsoft Internet Explorer takes web pages that are beautiful works of art and trashes them. Google picked up the ball and took the Mozilla browser engine and then had their programmers that they pay quite well, more than Microsoft ever paid any of their employees and had them embark on an internet solution that would eventually make everyone happy. Chrome now in 2017 is making the whole world happy in many ways. The ones smart enough to read and understand an options menu will be the ones to benefit the most. Chrome comes with default setting and they try to keep it set up in a default fashion that should allow even a child or mildly retarded person to comprehend.

Chrome did not insult their entire community of people by forcing a ridiculous zoom level that would trash web pages like FireFox and Pale Moon has done. CSS 3 and HTML 5 can do many things and not all of those things are supported by many browsers. Chrome is an exception to that rule because their programmers know what they are doing. Maxthon and Opera are very close seconds but have a long long way to go to catch up.

FireFox had come a million miles from back in the day when they were once known as Netscape, and later was so playfully dubbed NutScrape. Netscape and FireFox were loved by many but those days are now over. Just like when they killed Netscape, FireFox lies bleeding after a horrible blunder made by some young doofus programmer who is probably still young enough that mommy still makes him pancakes in the morning, driving daddy's car to work until he gets fired and has to get a real jobby. FireFox shot itself in the foot by insulting their entire community while they were using what they thought was an awesome browser. They have broken websites by forcing a zoom on the client side that is in no way correctable. You can't even adjust the browser back or reset it to the factory original settings as they have done away with them without even consulting with their end-user community, and then released it mainstream without even letting the folks run the beta testing it deserved.

I used FireFox for years and when they trashed a site that I visit on a regular basis I was done. FireFox is a piece of garbage now and it was that one little feature that soon enough will creep on every end-user. As a programmer, we have to develop CMS solutions that are supported by every browser and we were doing that just fine. We set the graphics and fonts the size they were intended to be. It's easy enough even for the doofus programmers... We drop a cookie and get the browser information and resolution and we design around that. We did not need for some young programmer who just does not have the experience he needs to make such a decision, one that would trash all the years of hard work that other programmers have done to get FireFox where it was up until recently when many sites loaded and graphics were out of place and no longer pleasant to look at.

Maxthon has come a million miles and is heading in the right direction as well as Opera. There is no future for FireFox or Microsoft IE they have made far too many mistakes and disrespected their community in a way that they will never be able to recover from.  Chakra JavaScript engine and Microsoft's Trident rendering engine (not WebKit) is a joke and always has been. Microsoft is saying the coming new browser will look and feel more like Chrome and Firefox and will support extensions. I hate to say this but we do not care at this point, Chrome and Google have a lot of money and the best programmers that big money can buy. Google has the attention of some the best programmers alive and it will remain that way from now until the end of Eternity. The future looks bright and the only browsers out there that can hold candles to light the same room are Maxthon, Chrome, and Opera. 

Sincerely,
Ernest Allen Buffington
ernest.buffington@gmail.com

I have added an SSL filter to the database query for all the Music and Blog content. The network strictly enforces SSL (HTTPS) and does not allow any unsecured data to pass. In the event that you post a link to unsecured data or an unsecured image, the server will automatically change the data on the fly. 

For example, if you post a YouTube link or an iframe by simply pasting it into the post window or edit box there are no worries because it will be changed from HTTP to HTTPS on the fly.

This feature wass added because a lot of people will be forgetting that the server is locked down tighter than Kelsey's nuts and will not allow anything that could pose a security risk to ever pass through ever at any given time.

If you think this was a great idea let us know by leaving a Facebook comment below.

Thanks and have a beautiful day!