So, I am working on MemProxy some. Mainly, I am trying to
implement more of the Cache-Control header's many options.
The one that has me a bit perplexed s-maxage. Particularly
when combined with max-age.
s-maxage is the maximum time in seconds an item should remain in
a shared cache. So, if s-maxage is set by the application
server, my proxy should keep it for that amount of time at the
most. Up until now, I have just been looking at
max-age. But, s-maxage is the proper one for a proxy to use
if it is present. I do not send the s-maxage through
because this is a reverse proxy and, IMO, that is proper behavior
for an application accelerating proxy. However, I do send
forward the max-age value that is set by the application
servers. If no max-age is set, I send a default as defined
in the script. Also, if no-cache …
I've been getting lots of inquiries from recruiters recently looking to find good people for various tech companies. Two in particular might be interesting if you're in the market or know someone who is.
Technology Evangelist at New York City Based Startup
If you saw Fred Wilson's post Are You A Connector?, you know a bit about this job already. It's a NYC based startup developing a new platform in an area that's likely to see serious growth in the next few years.
They're looking for someone with coding experience who loves showing other developers and users how stuff works: on stage, via blogs, in screencasts, and so on. It's important that this person have a technical (programming) background and also be very comfortable getting in front of people to demo and speak.
The company is New York based and this job is too. However, …
[Read more]
Project: MySQL Forge RSS/Atom feeds
KEY ACCOMPLISHMENTS LAST WEEK
* Integrated the RSS/Atom feeds on the website.
* Agreed on what to do next after finishing the feeds (Extending
PHPUnit test coverage)
* Found some items for the ToDo list (functionality on the Forge
which isn't complete working at the moment)
KEY TASKS THAT STALLED LAST WEEK
* Commit changes to main branch. I found out that the feeds who
are generated aren't 100% valid with the RSS 1.0, RSS 2.0 and
Atom specifications so I have to fix this before committing the
extension to the branch.
KEY CONCERNS
* None
TASKS IN THE UPCOMING WEEK
* Finishing the RSS/Atom feeds and merging them with the BZR
branch.
* Reading the PHPUnit documentation.
* Installing PHPUnit and exercise with the functionality.
|
|
Taking advantage of Launchpad excellent development services, I completed the tasks necessary to release MySQL Sandbox 2.0. So, you may ask, what's new? Quite a lot, actually:
|
more intuitive script names
One of …
Did you know that many parts of the MySQL web sites provide news and updates via RSS Feeds? Markus Popp from our web team did a great job on making some of these more visible by adding RSS icons to the respective pages. If you want to keep up with what's happing at MySQL, consider adding the following feeds to your feed reader:
-
New downloads on dev.mysql.com
- New DevZone articles
- PlanetMySQL (You probably knew that one already)
- MySQL Forge - All New Items
- …
Replication is one of the most flexible technologies available
for databases. We are implementing a new open-source,
database-neutral replication product that works with MySQL,
Oracle, and PostgreSQL. Naturally we've done a lot of thinking
about the feature set. It's tough to pick any single feature as
the most important, but one that really stands out is optional
statement replication. Here's why.
Database replication products tend to replicate row changes and
DDL. However, Mark Callaghan has a great example of why you want to replicate
statements as well--it enables Maatkit distributed consistency checking to
work. If you dissect the …
The modification of PDO_MYSQL to support the MySQL native driver for PHP (mysqlnd) is progressing. We are using the project title “PDO_MYSQLND” for the modification. The goal of PDO_MYSQLND is to provide a PDO driver for MySQL which can be compiled either against the MySQL Client Library or against the MySQL native driver for PHP. This is the same type of modification we did with ext/mysql and ext/mysqli already.
The use of any of the libraries is transparent for the PHP user. You may continue to use the MySQL Client Library, like you do today with PDO_MYSQL, or give mysqlnd a try. The MySQL native driver for PHP (mysqlnd) is easier to compile as its tightly integreated into the PHP internals and ships with PHP as of version PHP 5.3. In case of ext/mysql and ext/mysqli our benchmarks and first user feedback indicates that mysqlnd gives you at least the same performance of libmysql. And sometimes it is faster and more memory efficient. …
[Read more]The modification of PDO_MYSQL to support the MySQL native driver for PHP (mysqlnd) is progressing. We are using the project title “PDO_MYSQLND” for the modification. The goal of PDO_MYSQLND is to provide a PDO driver for MySQL which can be compiled either against the MySQL Client Library or against the MySQL native driver for PHP. This is the same type of modification we did with ext/mysql and ext/mysqli already.
The use of any of the libraries is transparent for the PHP user. You may continue to use the MySQL Client Library, like you do today with PDO_MYSQL, or give mysqlnd a try. The MySQL native driver for PHP (mysqlnd) is easier to compile as its tightly integreated into the PHP internals and ships with PHP as of version PHP 5.3. In case of ext/mysql and ext/mysqli our benchmarks and first user feedback indicates that mysqlnd gives you at least the same performance of libmysql. And sometimes it is faster and more memory efficient. …
[Read more]
The db4free.net's MySQL 6.0 server is at the very
latest state again. I have compiled the server from source, so
you can test the very latest of MySQL development.
Unfortunately there were some issues with the former version
(6.0.4) and I didn't manage to simply upgrade the server as I
used to. After upgrading, the server didn't start up with the old
data directory and dumping database by database to re-import it
into the new version resulted in frequent crashes. After multiple
failures to do a straight update I decided to install a fresh
and empty new 6.0 server.
Now the most important question for you if you used the 6.0
server: where did my data go?
I left the old server up and running, but configured it to port
3308. This means, if you had data in your MySQL 6.0 database, you
can still access it - here's how, if you use the default …
It's been a while since the last post. This is mostly due to me entering new territory in several ways. For one, I have been digging into JavaME development lately (platform change #1), building a mobile data entry and manipulation application that uses a an embedded database and talks to its server via Webservices, if connected. Otherwise data will be queued up locally and sent as soon as the