真是一个乱七八糟

 

出去玩了几天，

1 driver, 2 people, 3 time zones, 9 days, 11 states, and 4000 miles.

3+ national parks, 1 night of cabin, 3 nights of camping, and 4 nights of hotel/motels. 

 

Trivia:

1. No michigan plates found in ND, WY, nor NE.

2. The lake of Madison was dirty and smelly, at least in some areas.

3. Theodore Roosevelt is the fourth guy on Mount Rushmore.

4. Badlands was very windy.

5. Bear noise was not funny during night, bear stories were, actually, during the day.

6. Earth quake in GTNP is 2000-3000 years overdue.

7. Rawlins, WY has 15 Chinese in total, out of pop 9009.

8. I-80 has so many trucks, much more than I expected.

9. Taxpayers' money are actually at work, so many constructions on highways and parks, some more than 20miles long.

10. Trucks + contructions == delays. Bear in river == delays+delays+delays.  

    

 

看到电视上的预告片，探索频道的一个节目说他们在英吉利海峡找到了1744年的英国战舰残骸，战舰可能载有四吨重的金币。

 

思维奔溢一下，我想到了加勒比海盗电影里的那个指向你最想要的东西的指南针。如果有这样的指南针找这种残骸岂不是轻而易举？

 

不过对我这样的俗人来说，这样的指南针有没有这么大好处？列举一下我们可能想要的东西

1）平时用得上的或者用不上的，指南针十有八九会指向超市或者别人家里。然后我们去抢？

2）金银财宝，银行或者首饰店，接着抢？

3）帅哥美女，抢人？

4）名声地位，指南针估计会指向武器店啥的，好名声太难，坏名声比较直接了当。

5）发论文？？？难道是要去敲别人的脑袋瓜子抢人家的想法？

6）找人？还是打手机算了。

 

想来想去，这个东西还是在找找钱包，手机，或者遥控器更加有用。

 

 

 

祝大家都2009心想事成！

 

最近去了一趟新泽西，见见老朋友。特意挑的圣诞节之前去，希望可以避免在机场航班取消，晚点之类的烦心事。可惜还是没有躲过去，去的时候飞机晚点3个小时，说是天气原因。回来的时候飞机晚点两个小时，我到的时候飞机在我的目的地还没有起飞。

 

坐火车去找公司的同事吃饭，地图上说同事到车站需要15分钟，结果他被堵在高速上一个多小时。我在火车站转悠了一个多小时，始终觉得车站里面有一股炸油条的味道。。。

 

在等着无聊的时候发现我应该在自己的手机加上data plan来上上网。嗯，上网躲不过看email，还是装点游戏好了。

taken http://en.wikipedia.org/wiki/Tier_1_network

 

 

 

In Linux kernel, gettimeofday() can jump into the future for 4398 seconds in multi-core enviroment.

 

This is much worse than the "accept()" call, and as bad as the "debian ssh key" problem.

 

 

" I have seen this as well (on a 2.6.20.4 kernel). The value returned was
always identical each time the glitch occured (just a little over 4398
seconds). I saw it watching packet receive timestamps and on the system in
question, it would generally hit this problem around once a minute. When
moving forward to a 2.6.21 kernel, the problem seemed to go away (also back
to 2.6.17, unfortunately I didn't have any sample points inbetween)."

Taken from http://tompiselloroiguy.blogspot.com/2006/11/tca-champ-oracle-or-microsoft-sql.html

 

 

Microsoft SQL Server 2005 required significantly less effort to install and maintain than Oracle Database 10g. Study participants reported that on average a database administrator could manage over 30 Microsoft SQL Server 2005 databases, while Oracle 10g implementations required one DBA per 10 databases. On average, the annual cost for administration is $2,847 per year per database for Microsoft SQL Server 2005 and $10,206 per year per database for Oracle 10g, more than a 350% savings in annual costs per database for the Microsoft platform.

To assure similar comparisons, the study examined potential differences in the application, load and complexity of the database instances. As expected, the Oracle databases supported more users per database (2 to 1) and larger volume size (3.6 to 1) than the Microsoft databases on average. So it makes perfect sense that Oracle would be more expensive to manage on a per-database basis, but the costs were still slightly higher for Oracle than expected in comparison.

Comparing costs per user supported, we found that Microsoft SQL Server 2005 still has a TCA advantage on a per-user basis, $13.09 per user versus $18.05 per user for Oracle. However, when large-volume databases were examined, Oracle 10g had the lower TCA: $46.76 per gigabyte for Oracle 10g versus $66.58 for Microsoft SQL Server 2005.

Lower change costs, the cost to develop new database applications or migrating existing databases can be 20% to 30% of any database project’s costs and should be a major consideration. As well, the costs for hardware platforms, software licensing, management utilities and business resilience should be tallied, since these typically consume 40% or more of any database project’s cost.

 

 

 

Taken from http://en.wikipedia.org/wiki/Microsoft_Silverlight

 

Silverlight 1.0 consists of the core presentation framework, which is responsible for UI, interactivity and user input, basic UI controls, graphics and animation, media playback, DRM support, and DOM integration.

    * Input – handling input from devices like keyboard, mouse, stylus etc.
    * UI core – managing rendering of bitmap images (including compressed raster images like JPEG), vector graphics, text and animations.
    * Media – playback of MP3, WMA Standard, WMV7, WMV8 and WMV9/VC-1 streams.
    * XAML – to allow the UI layout to be created using XAML markup language.

A Silverlight application starts by invoking the Silverlight control from the HTML page, which then loads up a XAML file. The XAML file contains a Canvas object, which acts as placeholder for other elements. These elements can be animated using Event triggers. Events like keyboard or mouse movements can also raise Events which can be handled by custom scripts. Programmatic manipulation of the UI is achieved by using scripting languages to modify the Document Object Model of the Silverlight Canvas object.

 

Silverlight 2 includes a version of the .NET Framework, implementing the same full Common Language Runtime version as .NET Framework 3.0; so it can execute any .NET language including VB.NET and C# code. The XAML layout markup file (.xaml file) can be augmented by code-behind code, written in any .NET language, which contains the programming logic. It can be used to programmatically manipulate both the Silverlight application and the HTML page which hosts the Silverlight control. The XAML markup as well as the code, is compiled into .NET assemblies which are then compressed using ZIP and stored in a .xap file.

 

Sliverlight 2 adds support for network communication using sockets, over both IPv4 and IPv6. Sockets can be used for cross domain connections, but Silverlight uses an XML-based configuration file to control the cross-domain resource access policy, both for HTTP connections as well as socket connections. Silverlight sockets can only initiate a connection; they cannot listen for connections.

 

Silverlight 2 includes the Dynamic Language Runtime (DLR) which allows dynamic compilation and execution of dynamic (scripting) languages. Compilers for the languages based on the DLR (including IronPython and IronRuby) are be packaged with the DSL app in the .xap package.

 

Silverlight 2 also allows limited filesystem access to Silverlight applications. The file is sanitized of path information to prevent the application from getting access to information like user name and can be opened only in read-only mode. For local storage of data, Silverlight provides isolated local storage (isostorage), which is stored, outside the browser cache, in a hidden folder inside the user profile's private folder. It is by default set to 1 MB per URL. Data stored by a Silverlight application in the isostorage is identified by the URL that it loads from, can be accessed by that application only. All instances of Silverlight share the same isostorage, so all instances of the same Silverlight application can share the saved data, even if they are running on different browsers.