经济危机了，所以还没有开始找工作，实习大战已经开幕了。

我也投了几家自己非常心仪的公司，掂量掂量自己的水平吧。不过，这一掂量的确不怎么样。唯有继续好好学习。

我投了四家，两家参加机试，不过看来都算挂了吧，题目不是很难，但是有的不是遗忘，就是反应有些慢。还有一家是直接拒绝了我。最后一家参加了笔试，也有幸进入了一面。

面试中先是做了一个自我介绍，英文的。这个我准备了，不过要说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;
}

当机会砸在头顶的时候，却抓不住，只能是自己的悲哀。
                                                                             ——笔试后有感