經濟危機了，所以還沒有開始找工作，實習大戰已經開幕了。

我也投了幾家自己非常心儀的公司，掂量掂量自己的水平吧。不過，這一掂量的確不怎么樣。唯有繼續好好學習。

我投了四家，兩家參加機試，不過看來都算掛了吧，題目不是很難，但是有的不是遺忘，就是反應有些慢。還有一家是直接拒絕了我。最后一家參加了筆試，也有幸進入了一面。

面試中先是做了一個自我介紹，英文的。這個我準備了，不過要說5分鐘。

下面是詢問我做過的項目。面試官很nice，盡管他不是很懂我做的項目，還是一個一個的項目問，而且很耐心，不錯的面試官。

問完項目后，問了一些問題，有C++的，有數據庫的（這個只有一道，多年沒有摸過，忘得一干二凈，沒答上來），有linux(如何查看進程，我還是不會)。

那就只有C++，我還可以答上一二。

發現平常有時候，你知道的一些知識，有的覺得是這樣的，但當你去表達的時候，卻理不出來頭緒。此時的我就是這樣。看來基本功不是很扎實。

那個職位自己的把握也不是很大，中間有些東西自己說的不好，跟職位的匹配性也不是很好。

不過通過這次面試歷練，我覺得應該在一下幾方面注意一下：
1、對知識的掌握上，一定要很清楚，不能只知道皮毛性的東西。
2、在于對方的交談上，一定不要快速的回答問題，要給自己留一個思維緩沖的階段。能夠把答案稍作調理。
3、不要過多談一些想法，要有自己的想法。

被問到職業發展方向，這個真的不知道怎么回答，回來想想，還是很困惑，不過這倒給我提了一個醒，要好好規劃自己的人生，不能糊里糊涂的走下去。

我將來做什么呢？當程序員，或許可以出幾本書，總結一下自己的程序員經驗。這是我現在想到的。
至于方向么？數據庫，windows mobile，這個我真的還不是很清楚。

如果你對我有建議的話，那我先謝謝你了。

昨天在解決如何從與Active Sync的連接中斷開，連接wap網絡時遇到。這個問題還是沒有解決。有人建議將ConnMgr.exe關閉。這個方法我嘗試了，但是引來的問題是我的其他網絡也無法連接。嘗試了一下IE，它重新啟動了ConnMgr.exe，并且繼續走Active Sync網絡。這個機制怎么做到的，不是很清楚。

所以從SDK上查了一下ConnMgr.exe的介紹。

The Connection Manager application is ConnMgr.exe. It interacts with multiple device applications, such as Internet Explorer Mobile, to schedule and manage network connections. It maintains a list of all connection requests, their priorities, and the available Connection Manager configuration service providers per device.

When called by an application, the Connection Manager application must first determine the end-to-end paths from the device to the target network, for example, the Internet or a corporate network. Connection Manager does this by retrieving all possible connections from the Connection Manager configuration service providers, and finds all the paths from the device to the target network. For more about the service providers, see Connection Manager Configuration Service Provider.

When the Connection Manager application has found all the possible paths from the device to the target network, it uses Connection Planner to determine the best connection to the target network. Connection Planner determines which connection requests should be connected at a specific time and which paths those requests should use to connect to their destination. For more information about the role of this component, see Connection Planner.

Once a proper connection has been determined and established by Connection Planner, the Connection Manager application schedules this connection, taking into account other scheduled connections and their priorities and security levels. It enables multiple applications to use the same connection on an interval basis instead of establishing a separate connection, in an attempt to reduce the number of redundant connections. A device application might need to make a short connection at an interval of every few minutes, and Connection Manager must schedule these short connections. If there are several applications that need to use the same connection on an interval basis, Connection Manager can notify each application when another application has already established that connection.

For example, if five device applications request a connection to the same network at an interval of every half hour, this could result in up to 10 connections to the same location every hour. Connection Manager tries to schedule the connections so that only two actual connections are needed per hour.

When a network connection enters an idle state for a specified period, Connection Manager automatically disconnects the connection. This mechanism frees device applications from having to handle low-level connection tasks. When an application requests a scheduled connection to a certain destination network with a specified time period interval, the Connection Manager application wakes up the device application when a connection to the specified destination network is available, or at the end of each time period interval. In the former case, the application can make use of the available connection. In the latter case, Connection Manager does not establish a connection but just wakes up the application. It is up to the application to request Connection Manager to establish the connection to the destination network.

Windows Mobile 5 is so jam packed with cool new APIs that some of the smaller (but still very useful!) ones fall through the PR cracks.  Here are two that I just got remineded of by a post in the smartphone.developer newsgroup:

ActiveSyncStart & ActiveSyncStop

These device-side APIs do exactly what the names imply.  To kick off or stop a synchornization from a desktop app, just use CeRapiInvoke to call them.

     在工作中遇到這樣一個問題：CreateToolhelp32Snapshot 失敗，利用GetLastError獲得錯誤值是8，存儲空間不足，無法處理此命令。 
     查看我們的存儲空間，還有很多。這是為什么呢？

     昨天跑到MSDN上去問了一下這個問題，沒想到今天就有人給了我回答：使用TH32CS_SNAPNOHEAPS參數，既可解決這個問題。原因在于如果不采用改參數的話，有可能快照會占用整個堆的空間。

     于是我們的使用方式將變為：
     HANDLE hSnapshot = CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS| TH32CS_SNAPNOHEAPS, 0);

     目前我也只是簡單驗證了一下，OK。如果大家也遇到這種情況的話，不妨試一下。

Windows Mobile 常見進程解析

#include <iostream>

using namespace std;

int main()
{
  cout << "Hello, World!" << endl;
  return 0;
}

#include <iostream>

using namespace std;

class A
{
public:
  A()
  {
    cout << "Hello, World!" << endl;
  }
};

A a;

int main()
{
  return 0;
}

#include <iostream>

using namespace std;

int Func()
{
  cout << "Hello, World!" << endl;
  return 1;
}

int i = Func();

int main()
{
  return 0;
}

當機會砸在頭頂的時候，卻抓不住，只能是自己的悲哀。
                                                                             ——筆試后有感