Unlike IPv4, configuring and retrieving IPv6 information on a PC can be daunting. Depending on the configuration, multiple IP address might be returned by an IPv6 host. IPV6Configurator utility retrives and sets IPV6 addresses seamlessly.
Many times it is necessary to run background tasks when the system is idle. In such cases, the task scheduler can be used to schedule a task upon OnIdle condition. When the system goes out of idle say due to an user action, this task is immediately terminated.
When the on idle task is terminated, it's desirable to take an action. As windows OS provides no direct way to achieve this, it can be implemented by tracking the process termination.
In some client/server applications running on same box, a large amount of data may need to be shared. For example, an image acquisition application sharing the image with its clients. This typically involves a RPC mechanism duplicating data. Instead ReadProcessMemory and WriteProcessMemory APIs can be used.
What this means is a Process A can share its array with Process B without doing IPC except sharing its PID and address of the array.
If the need is just to do a cross process communication within the box, it'd be bit heavy to use frameworks such as WCF as it comes with a learning curve and complex setup. However home grown solutions such as messaged based implementation suffer from flexibility and heavy maintenance.
The simpleIPC framework tries to strike right balance with the interface based programming coupled with zero setup.
There are plenty of MBCS based legacy MFC applications out there that require CJK language support. Migrating to Unicode is not an option in these cases.
All the resources such as menus, dialogs, string tables used by the application are defined in the .rc file. To support a CJK language, system wide changes should be made and the CJK .rc file must be coded in a certain way.
Windows OS internally use lightning fast compression and decompression APIs. This can be used by user applications also.
For example, a 5 MB DICOM image can be compressed to almost 40% in 38 ms and decompressed in 8ms.
Windows OS uses Cache memory set aside for faster IO with disk. For example when an user launches an application for the first time, it's loaded into cache memory. Next time when user launches the same application it loads faster since it's loaded from the cache memory instead from disk. In 32 bit OS such as Win XP , the maximum cache size is about 960 MB and in case of 64 bit like windows 7 it's 1 TB.
User applications can also take advantage of this such that data can be directly written to cache memory and read from there.
Windows Operating system provides a host of facilities listed below that can be utilized by user applications.
- Overlapped IO
- IO Completion Port
- Windows System cache
- File Mapping backed by NTFS sparse file
No comments:
Post a Comment