作者:AnySQL, 订阅AnySQL, Oracle数据库恢复及服务, Sybase恢复, 磁盘及RAID恢复

    继手机上MSN了一把后, 又开始手机QQ了, 觉得QQ也是很不错的聊天工具, 只是新买的手机没有为手机IM考虑过, 习惯了电脑的键盘布局, 用手机输入起来很慢, 也不爽. 不知道有没有手机上的五笔输入法软件.

    有张每月包2GB的GPRS卡, 就玩玩吧! 到不是真的为了7x24小时在线, 而是为了时尚一把, 为了年轻一把. 再说用不掉这个流量, 心中难受, 总觉得便宜了移动, 极大地反应了我的劣根性. 接下来的事就是找个QQ软件了, 第一次下载的是QQWAP软件, 简单的界面, 没有分组功能, 用了几下就觉得不爽而删除了.

    继续找好用的手机QQ软件, 由于不熟悉下载的渠道, 先是下载了什么QQ2007公测版, 结果安装后, 腾讯公司已经禁止这个版本的QQ登录了, 花了大把的流量, 也没有装成功. 网上尽是这样的骗人的下载, 为了赚取流量来获得利益, 最后还到从官方的网站去下载吧.

    官方下载的QQ2007肯定是能用了, 却不是很喜欢, 因为太过于花稍. 集成了太多骗取流量的页面, 如QQ下载页面, QZone等, 在手机上导航时, 很容易产生客外的流量, 好象是一个一个骗钱的陷井, 使用的人实在应当小心. 很想有一个Tecent Messgner这样的界面简结的手机软件, 而不是一整套的QQ软件. 不知道会不会出手机TM?

    不过手机QQ也只能玩一把, 因为它不象手机MSN那样干净, 为了防止流量陷井, 还是少用吧.

相关文章 | Related Artiles

我要留言(当前0)

早上突然想起一句话，那是在yahoo工作时，杨致远第一次来中国yahoo的讲话：“yahoo看的不是一年两年内谁做得更好，而是看十年后谁依然是最好！” 这句话其实涵盖了很多意思，可以找到很多中国古代的经典词句表达同样的意思“卧薪尝胆”、“志存高远”、“君子报仇，十年不晚”等等。

从地域和文化差异上来讲，杨致远的这句话也体现了国内企业和国外企业之间的一些风格差异，国内的诸多企业和创业者均有急功近利的心态，总希望一年赚钱，两年发财，三年上市，他们常常为了眼前利益掏空资源，把最好摘的桃子先摘了，很少有企业会构思超过3年以上的产品计划和战略。有时候，这也是国内的现实情况造成，强大的市场竞争压力造成企业必须先想办法活下去，对于创业型的企业来说，也没有太多好的选择。

但是对于一些已经做大的企业来说，这是非常重要的课题，比如百度、新浪这样的国内巨头，尤其新浪，面临的危机我个人认为很严峻，过于复杂的股东结构、过于分散的股份组成、加上CEO的角色任职结构，导致如今的新浪，没有任何长远发展战略，几乎都是在一直吃老本，而且挖空心思的吃，未来的新浪，很堪忧！

今天早上碰巧看到一篇李开复的报道，几乎表达了同样的意思，“我们希望在五年的时间内能够成为中国搜索市场的龙头”，五年，对于互联网来说真的是不短，google的战略清晰而务实，为了这个object，成熟的google必然有着一系列的计划和准备，在这个层面上，我对google在中国的信心依然很足，结果也许不会期望那么完美，但是我喜欢这样的风格。

前一段用SQL实现了一个复杂的功能，但是留下了一个问题一直没有真正的解决，那就是如何同时为表中的多条记录分别实现构造结果集。问题源自：一个复杂问题的求解过程（一）：http://yangtingkun.itpub.net/post/468/456641感觉直接用文字描述比较困难，下面通过一个例子说明打算实现什么样的功能。在写一个复杂的SQL的时候，经常会涉及到构造结果集的功能，而构造的功能一般是通过两种方法来实现，第一种是借助一张已经存在的大表，比如DBA_OBJECTS，通过访问这张表来获取需要的记录，第二种方式是利用CONNECT BY方式直接从DUAL表获取。第一...

An interesting side-effect of YouTube's recent push for higher quality videos is that most videos can be downloaded as MP4 files directly from YouTube. Until now, you could only get FLV files from your browser's cache or using one of the many websites that let you download YouTube videos. In fact, to download the MP4 files, you need to use the same URL like for FLV files and append "&fmt=18":

http://www.youtube.com/get_video?video_id=ID&t=SIGNATURE&fmt=18

ID is the video's identification value, SIGNATURE is a value that prevents you from downloading the file just by knowing the ID. You could create this URL by looking at the source code of a YouTube page, but it's much easier to automatically generate it.

One way is to save the following link as a bookmarklet by dragging it to your Links bar (in Firefox, Safari) or right-clicking and adding it to your favorites (in Internet Explorer, Opera):

Get YouTube video

If you didn't manage to add the bookmarklet, this post has more detailed instructions.

When you want to download a YouTube video, click on the bookmarklet and you should see a new option below the embeddable code.


Because YouTube doesn't send the right MIME type, you shouldn't click on the download link. Right-click and select "save link as" or "save target as" and enter a proper name for the video. Make sure to use the .mp4 extension when you enter the filename.


Having to click on the bookmarklet is annoying, so this Greasemonkey script is a better alternative because it adds the download link automatically. It requires the Greasemonkey extension for Firefox or a similar plug-in for userscripts. Opera has built-in support for userscripts, so you only need to go to Tools > Preferences > Advanced > Content > JavaScript options, select the directory where you will put your script and copy the script to that directory.

YouTube's MP4 files have a higher resolution, stereo sound and can be played with applications like VLC, MPlayer, iTunes, QuickTime. Not all YouTube videos can be downloaded as MP4 files and the fallback format is FLV.

Note that YouTube's terms of use require you "not to access User Submissions or YouTube Content through any technology or means other than the video playback pages of the Website itself, the YouTube Embeddable Player, or other explicitly authorized means YouTube may designate," so these scripts could break YouTube's policies. The scripts only download files that are used by YouTube's player, so you may also find the videos in your browser's cache.

Meet Bela Ban, a developer who began the JGroups and JBoss Cache projects. He’s now the technical lead of the JBoss clustering team, continuing the work he began as an college instructor.

Ban talks about the background of both projects, as well as upcoming developments, including increased throughput, persistence, security, remote accessibility, and other features. He also discusses the business needs that can be solved with these tools–just a small sample from his talk at JBoss World.

Yesterday I had a chance to speak to Igor - head of MySQL optimizer team and Timur - both of them expressed concern with TPC-H run results I posted and notes about little gains in MySQL 6.0.

Do not get this post wrong. I’m not saying MySQL 6.0 SubQuery optimizations are non existent or priorities were wrong, what I’m saying is just they do not seems to be apply to most of TPC-H Queries. I personally (before doing what exactly queries are part of TPC-H) was expecting to see gains in TPC-H and I think this is what other users would expect as well because this is well known set of complex queries which use SubQueries.

So what is the reason ? Why TPC-H queries are not targeted ?

The reason is MySQL Optimizer Team did not have the goal of optimizing TPC-H queries or queries from any other benchmarks, rather they look at the queries which MySQL Users have problem with and first target the most common issues. I think this is a great approach to pick what needs to be done first.

Another reason is “Derived Tables” AKA “Subselects in FROM Clause” are not optimized yet even though some optimizations may make it into final MySQL 6.0 release.

Summary: Poor MySQL 6.0 performance on TPC-H queries does NOT mean to quantify MySQL Optimizer Team work in any way:)

---

Entry posted by peter | No comment

Add to: | | | |

Yesterday we started the conference early with MySQL Community Dinner which was quite a success with about 30-50 people showing up (hard to count as people come and go) even though it was conflicting with Silicon Valley MySQL Meetup and which at least prevented Jeremy and his team showing up.
UPDATE: What I was thinking… There the meetup is today, but still I did not see Jeremy on the party yesterday.

To my surprise Jonathan Schwartz (Sun CEO) and Rich Green (VP of Software - boss of Marten Mickos) showed up and showed up at exactly right time - when we were discussing how the bill should be handled for such event. Rich Green introduced himself with something like “We just bought the company for 1 Billion so we can afford to pay for community dinner” and earned a round of applause.

It was great to have a chat with bunch of MySQL and MySQL Community guys, in particular with Mark Callaghan from Google about his experiences of using MySQL and work he does to scale MySQL and make it Highly Available. One of fun things I learned is Google actually patches MySQL 5.0 to make SubQueries to be disabled on parser level because they are generally poorly optimized and it is hard to ensure users do not use queries which MySQL does not optimize well. Also Mark told about failure rate of MySQL/Innodb which is about once per 1000 machine days (so if you have 1000 machines you will have approximately one crash per day) and he finds this quite good. Though I do not really remember if this applies to “cheap” hardware or “server grade” hardware class.

Sun Executives also of course got fair amount of attention. It is not so often you get a chance to have a private talk with CEO of 40.000 employees company. Initially we got MySQL Guys queued around them while later other people also had a chance to chat. Things worth mentioning is - Sun wants MySQL Community to be happy and if we see something what is done which hurts MySQL community Rich would like to get an email about that. They also listened carefully to complains regarding broken MySQL Community release process, from various people including Lenz Grimmer and promised to
take a look at that.

Another interesting note from Sun guys were what they are interesting in growth of MySQL User Base - “when someone uses MySQL it is good if he does not pay us, because this means he is not using something else” - not only number of paying users.

What was very surprising for me to hear Marten Mickos is also now responsible for PostgreSQL efforts inside of Sun. I do not think this makes much sense but lets see how it works out.

I personally left earlier to get some more work on the slides so there could be something else “fun” happened on the party.

---

Entry posted by peter | No comment

Add to: | | | |

Here is a brief analysis of the pre-release announcement for the upcoming April 2008 Oracle Critical Patch Update (CPU) -

• Overall, 41 security vulnerabilities are fixed in this CPU, which is an average number well within the range of previous CPUs (Jan-08=26, Oct-07=51, Jul-07=45, Apr-07=36, Jan-07=51, Oct-06=101, Jul-06=62, Apr-06=34, Jan-06=80).
• This is the first CPU that includes fixes for Siebel.
• The product and vulnerability mix appears to be similar to previous CPUs.  All CPU supported Oracle Database, Oracle Application Server, Oracle Collaboration Suite, and Oracle E-Business Suite versions are included.  The list of supported versions is getting very short and should be carefully reviewed to determine if version upgrades are required prior to applying the CPU security patches -
• Database = 9.2.0.8, 10.1.0.5, 10.2.0.3, and 11.1.0.6 for major platforms
  
• Application Server = 9.0.4.3, 10.1.2, and 10.1.3
• E-Business Suite = 11.5.9, 11.5.10.x, and 12.0.x
• The major CPU version support changes for April 2008 are -
  
• Database version 10.2.0.2 is only supported for Solaris x86 and VMS
• Oracle E-Business Suite 11i will require ATG RUP5 or RUP6
• Oracle instituted a new policy with the July 2007 CPU in that platforms with few downloads of CPU patches will not have patches proactively created -- the CPU patches will only be available upon request.  According to the January 2008 CPU note (Metalink Note ID 466757.1), patches for database version 10.1.0.5 on several platforms will be available only upon request for the April 2008 CPU.  For the Oracle Application Server, many platforms have "On Request" patches across all versions, especially 9.0.4.3.  The database note for the January 2008 CPU will have a section titled "Planned Patches for Next CPU Release" that should be carefully reviewed to determine if your platform/version will be an "On Request" patch in the next release.
  
  

Oracle Database

• There are 17 database vulnerabilities and two are remotely exploitable without authentication.  Since APEX, Net Services, Authentication, and UltraSearch are included as affected components, it will be very interesting to see where the remotely exploitable vulnerabilities lie.
  
• At least one of the database security vulnerabilities has a CVSS 2.0 metric of 6.6, which for database vulnerabilities should be considered high risk.  This typically means anyone with a valid database session is able to compromise the entire database, but is unable to achieve root operating system access.
• According to the January 2008 CPU notes, there is very limited platform support for 10.2.0.2.  Only the following platforms are supported for 10.2.0.2 by the April 2008 CPU: Solaris X86 and VMS.

Oracle Application Server

• There are 3 new Oracle Applications vulnerabilities, all of which are remotely exploitable without authentication.  Two impact the Oracle Application server components Oracle Dynamic Monitoring Service and Oracle Portal.  The third vulnerability is in Oracle Jinitiator, which is a client installed product.
  

Oracle E-Business Suite 11i and R12

• 7 of the 11 vulnerabilities in the Oracle E-Business Suite are remotely exploitable without authentication.  Most of the vulnerabilities are in core components like OA Framework and AOL, so all implementations should consider most of these patches as important.
  

Planning Impact

• As with all previous CPUs, this quarter's security patches should be deemed critical and you should adhere to the established procedures and timing used for previous CPUs.

Note: The pre-release announcement is removed when the CPU is released.