Chome chrome_installer.exe download location for DEV builds?

Hello!

I'm not sure if you can assist me but I'm trying to figure out if there is any logic to determining the new locations of the the version#_chrome_installer.exe on the Google edge download servers.

I keep on eye open over at the http://googlechromereleases.blogspot.com/ blog and look for new DEV build version releases.

In the past I just download the Windows binary file directly rather than going through the online updater process with the PAF file. Once downloaded I would extract it with 7zip and then manually update my portable apps Chrome DEV build. Habit I guess...as I suppose there isn't any logical reason not to use the PortableApp builds when they come out for a new DEV release version.

I had been getting them successfully using the following pattern as obtained with the build ID in these notice posts:

http://dl.google.com/edgedl/chrome/win/23.0.1243.0_chrome_installer.exe

However in the past few months Google changed that download pattern.

I can see from Wireshark packet-traces (and looking in the PAF ...\GoogleChromePortableDev_24.0.1312.1_online.paf\$_OUTDIR\AppInfo\installer.ini file) that they are now placing the download location in what appears to be a "randomized" sub-folder location each time.

For example, the *_chrome_installer.exe file has recently been placed in the following locations:

http://dl.google.com/edgedl/chrome/win/C8E013218C8F141C/24.0.1297.0_chro...

http://dl.google.com/edgedl/chrome/win/2BB82C5AEBD3728F/24.0.1305.3_chro...

http://dl.google.com/edgedl/chrome/win/209C8A1344567BFE/24.0.1312.1_chro...

I know that the maintainers of the PortableApps Chrome Dev build have been able to keep them current so I'm wondering and hoping for someone to clarify so I can better understand if there is some pattern/logic behind the new sub-folder location. Is it truly "random" or some ROT or other conversion of a particular value?

I'm probably missing something obvious...

I think I've been using this manual-direct download method to get the DEV builds super-quick upon release. I can monitor their release from the Google Chrome Release blog via my RSS feed reader. I haven't been able to find a "PortableApps" RSS feed that I can use specifically to monitor new PortableApps Chrome DEV build release notices. So now I have to monitor the RSS feed for the Google blog, then periodically drop in on the PortableApps Chrome page and scroll-down to see if it has been updated to the new version yet.

Can anyone please share if there is a logic to the new direct download location? Or if not, what process at PortableApps is used to determine that location when a new DEV build is released? Does Google have a public location notice published or index available?

If not, is there a way or possibility to add PortableApps RSS feed notice for when the Google Chrome DEV/Beta builds also get updated so I can monitor for that directly? Or if it is already there, where I can find it?

I appreciate and value all the hard work the PortableApps team and supporters do. My hope is someone can shed some light on a way to monitor for and/or get the latest Chrome DEV bits quickly to update my portable apps build of it.

Thanks for your feedback!

--Claus V.