tag:blogger.com,1999:blog-75639569001585744472008-09-25T13:15:33.339-07:00GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comBlogger23125tag:blogger.com,1999:blog-7563956900158574447.post-11359669777128665832008-08-01T09:41:00.000-07:002008-08-01T09:46:06.531-07:00

On a Linux web hosting account this works great: Open a text editor (Notepad) Paste this into the file: RewriteEngine On RewriteRule ^app/([A-Za-z0-9_-]+)$ index.php?app=$1 [L] Save the file as .htaccess Upload it. That's all there is to it. Reference: http://www.sourcerally.net/Scripts/42-Web---Root-Directory

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-73870332229362080242008-05-31T12:40:00.000-07:002008-05-31T12:50:16.676-07:00

... For any traffic that you intend to load-balance please be sure you have DNS pointed at the load balancer's virtual IP (VIP). In order to properly configure your load-balancer we will need to know which servers (also specify which IPs on which servers) you wish to have load-balanced and which types of traffic you will be load-balancing. The most common scenario is to load-balance WWW (TCP

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-24576576810110264552008-05-31T00:51:00.000-07:002008-05-31T00:59:35.785-07:00

Are these canned email replies to trouble tickets really necessary? Most people would just think it's an emergency because their site is down -- it's just simply UNAVAILABLE! But I guess if the help just isn't there, you're SOL... Seems to me though if you're in a managed hosting situation, someone on their side should know your site is down before you call. This automated response is to

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-36311176177012866582008-05-31T00:46:00.000-07:002008-05-31T00:47:06.842-07:00

In regards to using BINARY over CHAR, while this might be splitting hairs in terms of performance, the BINARY option is going to be more efficient in multiple fronts. The reason is that if you store an MD5 as a string, it requires 8 bits per character. But you are actually only representing 4 bits per character. If you store the string in binary, you can half the size of the field. It is also

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-88925589236218133782008-05-31T00:13:00.000-07:002008-05-31T00:19:08.563-07:00

To figure out the right settings for your database server, you really need a good MySQL DBA to take a look at your application's resource utilization and make decisions based on hard data. Preliminary assessment for our current set up - after yet another crash: My guess would be that the mysqld service crashed while writing to the table. Being as mysql is using 6G in global buffers alone and

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-40286781842643418372008-05-30T23:57:00.000-07:002008-05-31T00:06:21.583-07:00

Notes from a MySQL DBA: With MyISAM tables, updates/insert cause table level locking. Converting to InnoDB will be useful as this uses MVCC + row level locking. Things that can be done: Convert to InnoDB Create a numeric PK (auto_Increment) and UNIQUE KEY for hashid. InnoDB require primary keys (PK) for all your tables. If you don't define one, one will be invisibly defined for you. InnoDB best

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-12765818698386499752008-05-30T23:43:00.000-07:002008-05-30T23:52:30.968-07:00

When you develop a web application that is database driven that is going to log a lot of data, you really have to consider the database structure carefully. Here's an example of how a log table was optimized. This table had over 60 million rows and getting another million rows a day! -- The problem with this table (in terms of speed) is that It’s quite large (62M rows) It’s heavily indexed.

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-85869090981035077862008-05-30T23:24:00.000-07:002008-05-30T23:39:21.311-07:00

Most developers will never run into this situation. But if you're running a Linux server RHE 32-bit OS and have a large MySQL database, watch out! It took a few days of crashing this database with a table that has over 14GB of data. The index on that table had grown over 2GB and was causing MySQL server to page the data (writing temp data to the hard drive instead of RAM). Disk I/O is thousands

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-81588710459349600412008-05-09T18:11:00.000-07:002008-09-25T13:15:33.365-07:00

I just looked at pretty much everything available out there. I like this one the best, and it's free. This is just a simple add-on that will give your cmd.exe additional functionality like ssh. I've used it on Windows 2000 and Windows XP. Download copSSH - OpenSSH for Windows from http://sourceforge.net/project/showfiles.php?group_id=69227&package_id=127780&release_id=615115 copSSH is an

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-51912782695402149322008-05-09T14:08:00.000-07:002008-05-09T14:36:11.590-07:00

When your database is large enough that using phpMyAdmin is not feasible, you can use mysqldump to move a database to a new server. This looks like a reasonable tutorial, which came up with a google search: http://www.mydigitallife.info/2007/07/21/how-to-backup-and-restore-export-and-import-mysql-databases-tutorial/ Essentially all you do is: # mysqldump dbname > whatever.sql -- or -- #

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-72221608959370655252008-05-07T18:27:00.000-07:002008-05-07T18:33:32.194-07:00

I noticed this in my logs. Looks like when you use your Adwords account to analyze your ads and upload a campaign, Google sends a bunch of queries to analyze your landing pages. And it's not just the AdsBot, you also get the actual Googlebot visiting as well... Interesting. 05/07/2008 12:32 AM Mozilla/5.0 (compatible; Google Keyword Tool; +http://adwords.google.com/select/KeywordToolExternal)

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-90680419298005701912008-05-06T18:58:00.000-07:002008-05-06T19:25:03.085-07:00

It seems the Google Adwords API doesn't give you consistent results for cost and traffic data. The numbers can change radically during the same 24hr period. How are we supposed to get reliable stats from this? Here's the response from Adwords staff: Using getNewKeywordEstimate() function is not the best choice if you want the most accurate estimates. When you use estimateKeywordList() method,

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-28199697871250612882008-04-25T23:22:00.000-07:002008-04-25T23:43:18.612-07:00

Looks like a useful class for handling CSV files. I haven't tested it yet. filePointer = fopen($file, 'r'); $this->delimiter = $delimiter; } catch (Exception $e) { throw new Exception('The file "'.$file.'" cannot be read.'); } } /** * This method resets the file pointer. * * @access public */ public function rewind() { $this->rowCounter = 0; rewind($this->filePointer); }

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-77189582423392049322008-03-21T10:59:00.000-07:002008-03-21T11:08:53.891-07:00

If you've never submitted a PPC campaign to MSN, get ready for some real scrutiny of your landing pages... A campaign that was successfully launched with Google and Yahoo got this response from MSN editors: Here some information regarding QBR and landing page best practices. From here, we need to rework your landing page to clean it up a bit. Then I'll appeal the QBR status. Hope this helps.

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-86648531816268362712007-12-20T13:00:00.000-08:002007-12-20T13:09:47.468-08:00

There was a problem with the SSL certificate... When I opened https://www.silopublisher.com directly after opening Firefox (Windows XP Home) I got the following notice - see attached. This error wasn't showing up in IE7. Only with Firefox... Here's the response from Godaddy: Support Staff Response Dear Secure Certificate Customer, Upon reviewing your site, I have found the problem

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-78459403018997150482007-10-20T12:05:00.000-07:002007-10-20T12:07:43.203-07:00

Red Hat Linux has a tool that collects data installed, to view the data you can use the sar command from the command line. To find out how many processes were running and the one minute, five minute and fifteen minute load averages you can type 'sar -r' (without the quotes). To find out RAM and swap disk memory usage you can type 'sar -q' (without the quotes). To look at I/O statistics you can

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-56898301164922803062007-06-21T12:03:00.000-07:002007-06-21T12:11:31.856-07:00

This code block will work for Godaddy hosting accounts that require outbound connections via their proxy. curl_setopt($ch, CURLOPT_VERBOSE, 1); curl_setopt($ch, CURLOPT_URL, $url); curl_setopt ($ch, CURLOPT_PROXYTYPE, CURLPROXY_HTTP); //"http://64.202.165.130:3128" curl_setopt ($ch, CURLOPT_PROXY,"http://proxy.shr.secureserver.net:3128"); curl_setopt($ch, CURLOPT_TIMEOUT, 30); curl_setopt($ch,

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-11760985348156630662007-06-14T10:44:00.000-07:002007-06-14T10:57:42.236-07:00

Finally. After a 2-week wait. Your AdWords API tokens have been approved!Congratulations! Based on the information you provided during registration, your Developer Token and Application Token have been approved and activated for use with the AdWords API. Your approved tokens are on your AdWords API Center page (see Account details below). In the meantime, if you haven't already done so, you

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-51395256917952155382007-06-14T09:08:00.000-07:002007-06-14T09:17:46.355-07:00

Recently ran into this site: http://www.dhtmlgoodies.com/ This site has a bunch of really cool scripts - AJAX, DHTML / PHP - with demos. Check out their regular expression checker: http://www.dhtmlgoodies.com/scripts/regular-expression/regular-expression.html Pretty cool. -j

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-51058009143801067782007-06-03T01:29:00.000-07:002007-06-03T01:40:46.656-07:00

Got this error while testing code for the Adwords API using the Sandbox: Message: The specified client email does not exist. Your client accounts may not exist because either this is your first time using the sandbox or the sandbox database has been cleaned. Please remove the clientEmail from the request header and call the getClientAccounts method from AccountService to ensure that your client

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-8275353166020705372007-05-04T17:44:00.000-07:002007-05-04T18:03:31.148-07:00

Are you still obsessed with PageRank? GoinfoSystems.com and SiloPublisher.com didn't have any PR until recently. Yet we were getting traffic for some nice long-tail keywords. Mostly from Google. For example, Google the phrase lsi web publishing. Silo Publisher is on 1st page out of over 500,000 results. This is what the site is about after all. So it makes sense. But we have virtually no

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-47009114701839109062007-04-24T00:26:00.000-07:002007-04-24T00:41:37.292-07:00

We're planning a lot of exciting projects to enhance Silo Publisher and related applications. With growth comes new challenges for stability, scalability, and long-term maintenance of our own code. Moving toward a more standards based environment is an obvious choice, but one that involves rewriting some of our own applications. Hopefully it's still early in the game for us. It's better to be

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.comtag:blogger.com,1999:blog-7563956900158574447.post-85159506011787192962007-04-17T14:16:00.000-07:002007-04-17T14:24:11.032-07:00

We're finally on the home stretch to do a major launch for Silo Publisher. It's amazing how this application has grown over the past few months. Not only on the backend programming side, but also with our strategic partnerships the best in the industry. Theme Zoom, University2020.com, and ... a soon to be public PPC management service. We will soon be able to unveil exactly how our services are

GoInfo Systemshttp://www.blogger.com/profile/01944028534297622087noreply@blogger.com