Is anybody aware of a piece of software bridging MAPI and ActiveSync ? Preferably open source. Or alternatively, a MAPI <-> IMAP solution could work.
I've never used it, but it looks like Z-Push fits your needs. It's open source and bridges ActiveSync to IMAP.
Related
I wanted to know what mobile devices(Mobile phone and others) are available in the market which supports OMA Lightweight M2M protocol. As its a new protocol released this year but there is no information on the internet about available devices those support this protocol. As i wanted to make Proof of concept therefore i need to have device to do so.
OMA LWM2M is indeed so new that it is not yet an official OMA enabler.
You can find an open source implementation here: liblwm2m. It is not feature complete (bootstrap interface is missing) but you can make proof of concept out of it.
The complete Lightweight M2M spec is now available for free from OMA at http://openmobilealliance.hs-sites.com/lightweight-m2m-specification-from-oma
Currently, OMA try to provide many helps to the developers. You can refer to https://github.com/OpenMobileAlliance
And there are some open sources as refer to
http://www.omaevents.org/?page_id=1626 which is recent event.
What is needed to design on windows a driver for bluetooth mouse?
Do I need to use .NET framework for that? and do I need to create my own code from scratch is there an existing windows-based api for designers
You will definitely need the Windows Driver Kit to provide you with the necessary APIs.
And .NET won't come in handy there, you will be working with pure C, maybe C++.
Additionally you will need to know about the BT-stack, which is proprietary. Creating Drivers is no piece of cake, definitely. Maybe look for a user-space BT-library.
Is thit true that all browsers on windows OS work thru winsock? thanks
I think that all the browsers use actually Winsock2. It has several extensions over Winsock, most are related to the support of overlapped (asynchronous) I/O on sockets.
Specifically MS Internet Explorer uses a higher-level library called WinINet. Which in turn of course uses Winsock2.
I don't know for a fact that they all do (what does "all" mean, anyway?) But what else would they use? Winsock is the Windows Sockets API, through which access to network cards is mediated.
I want to make a windows application in which I want to send ,receive and process SMS using GSM Modem( this one ), It would be very helpful If you provide me link to any opensource library or application which do the same. I am good in MFC and Qt, so any C++ or C library or app reference would be much better.
It would be great help, If you can tell me/Give some reference of how to do incoming call processing. I want to read user's keyboard input during call ( Like press 1 for Apple and press 2 for Microsoft ). As in next version I want to support this.
For the SMS part you can use the open source Kannel server. It will work with GSM modems and provide an interface (HTTP) for your application to interact with it.
Call wise, you are probably looking for an IVR solution. You can write the branching logic (voice menu, press 1 etc) in its language. Asterisk seems to support that but I have no experience with it.
Java library SMSlib can do it for SMS and USSD. Unfortunately, MMS isn't supported.
I need some advice on windows programming, MIDI and WDM. I am trying to write a small application that will sit in the sys tray and be advertised to the system as a MIDI In/Out device so that MIDI programs can send to it and it will convert the messages into a different format. I have been reading Cant's WDM book and scouring for information about writing device drivers, but don't know if I'm going down the right path.
I don't see yet how to:-
a) register my driver as MIDI capable (do I stick a ref to it in the registery and let the OS direct MIDI calls to the functionality in a dll?)
b) direct MIDI data through the my driver to my app, which is probably going to be too large to be a driver itself.
Any advice on where to start would be much appreciated.
thanks,
Pete
Windows MIDI drivers do not need to be implemented in the kernel, they can be implemented entirely in userspace as DLLs.
MSDN has some information about the functions you need to implement -
Audio Device Messages for MIDI - unfortunately it is somewhat lacking.
There used to be sample code for this kind of driver, as part of the NT4 DDK, but more recent releases of the DDK / WDK unfortunately don't include it any more.
Some better (though older) documentation and sample code can still be found after some searching:
Introduction to Multimedia Drivers (From NT4 DDK)
Sample MIDI Wine Driver for Mac OS X
Devices are enumerated (or simulated) by device drivers, not applications. What you see in the sys tray is an application icon. Hence, you will need to have both a driver and an app - you can't have one bit of compiled code acting as both.
On the driver side, you probably want to have a peek at the MSDN docs. This will answer part (a) of yopur question.
Assuming that you still would like to continue, (b) is best don by letting your application pull the data from the driver. That's far easier than the other way around - an application can trivially find a driver, but a driver has big problems finding a specific app (process)
If you are looking for a bit easier way to get started, there is a MIDI loopback driver out there, and the folks that make it also offer (or used to offer) a version of it that allows your program to communicate directly with the driver. This gives you the behavior you are looking for, where a program appears as a MIDI device. The loopback driver is at http://nerds.de/en/loopbe1.html. I don't see the developer page anymore, but if you contact them, you might be able to purchase a license to a driver that you can access directly without the loopback.