Can anyone advise me how through an example, or whether it is possible to generate SNMP events in .Net using Framework 2.0 and for those events to be monitored using windows tools?
Thanks
SNMP protocol does not define anything called events. Do you mean by notifications? An SNMP engine/agent can raise notificates (TRAP or INFORM messages) over UDP to its dedicated SNMP managers, so that the managers know something happens.
If that's what you mean, you may use any SNMP library that supports .NET 2.
http://www.lextm.com/2007/12/product-review-snmp-libraries-for-net.html
But .NET 2 is too old, and even Microsoft no longer supports .NET 2 unless you are also installing .NET 3.5 SP1 on the same machine. Therefore, you may consider targeting .NET 3.5 directly instead of 2.0.
Related
Different services version could support different features.
For example version 1 of service not support feature x, but version 2 support feature x.
Is there are some standard or practical way to inform which features are supported in current service version?
I think to some way that information could be obtained from commit descriptions. Is there some standard to obtain that information? Or should every service inform about it in own way.
Or should every service inform about it in own way.
Don't do this. This will couple your service with others. Others shouldn't know how to handle your version, but you should know how to handle different versions.
If you use REST and synchronous communication between microservices, you have to look at REST API Versioning or here. This type of versioning allows you to have multiple versions running in the same infrastructure. Then, each microservice should know how to call a specific version of a microservice.
If you have asynchronous communication with an Event Bus, then your Emitter should send backward-compatible events, to not break other microservices.
I'd like to use both Google's Native-client API and BlueZ for a senior design project but, I can't figure out if BlueZ is compatible the Native Client SDK. Does the full set of white-listed APIs include this library?
I'm uncertain if bluetooth APIs in general are white-listed for Android Native Client apps, but even if they are, there are not going to be native BlueZ APIs available on all devices or versions.
As indicated by Google (https://source.android.com/devices/bluetooth.html) as of JB 4.2 the native bluetooth stack is BlueDroid, which is based on Broadcom's stack. Before that time BlueZ was the default stack, but was replaced by some vendors with their own.
It may still be possible to install BlueZ on your newer OS device if it is rooted, but you cannot at all be certain the underlying stack on any random device will be BlueZ or BlueDroid, so if developing an app for distribution you would need to limit yourself to official APIs that Android provides (http://developer.android.com/guide/topics/connectivity/bluetooth.html), or maybe implement on each stack and detect at runtime what stack to use, assuming what you want to do is even possible with BlueDroid.
Does Google Glass SDK (GDK) support BLE yet? I would like to connect and communicate with a Bluegiga BLE113 module.
Thanks.
Yup! It was added with the upgrade to Kit Kat in XE16.
The feature request was closed as fixed when that release was pushed out.
According to this article with the FCC filing, yes, it does. However, Android 4.0.4 does not natively support BLE, so unless the Glass Team built a BLE library for Glass, no, it doesn't. I'd suggest testing (if you have Glass). If not, I can test for you to check, if you have a way.
Actually, according to Android doc it is available from API Level 18 (4.3). I can't wait to see an Android update for Google Glass.
I know that VB offers many things to control it : SDK, API, COM, web server etc
What I'd like to do is have a GUI to simply create VM connected through networks but I have to know: what is the best solution use Frontends [1], webserver, COM* or API ? elsewhere libvirt ?
A an example a use case could be : I put 3 VMs on my GUI, choose their respective OS , create 1 or more network connection(s) for each and connect these VM to create network(s).
Python, C++, etc, implementation language doesn't matter.
[1] http://www.virtualbox.org/manual/ch01.html#frontends
My qualifications for answering this being that I created and have maintained Vagrant since early 2010. Here are my general opinions of each of the available frontends for scripting VirtualBox:
vboxwebsrv is the VirtualBox web service which provides an API to control VirtualBox. The pro of this is that web services are easy to program for nowadays. The main con is that you must handle startting and stopping this web service manually (or check to make sure it is already running). Historically, the web service has not been fully up-to-date with the latest APIs available in each version of VirtualBox, but I'm not sure what the status of that is today.
COM or C API. VirtualBox provides an XPCOM based API on non-Windows platforms and an MSCOM based API on Windows. If you can't use C++, you can also use the C API on Linux (but it is not available/exported on Windows). I used this API for over a year. Pros: Fast and complete. Since it is a C API it is very fast, communicating with the VirtualBox process directly. It is also complete, since this is the same API that VirtualBox GUI is using as well as using internally. The main con is that XPCOM is not easy, and the C API is not available on Windows, meaning you either have to pain through XPCOM, or you need to handle both C and MSCOM. I chose the latter and it turned out to be a nightmare of compatibility. Almost every minor release of VirtualBox (3.1, 3.2, etc.) will change the API in a backwards incompatible way (slightly) and a major release and you can completely forget about (3.0, 4.0, etc.). This makes handling older versions of VirtualBox... tricky. This is definitely an advanced use case.
VBoxManage is the CLI based frontend for VirtualBox. Under the covers VBoxManage is of course just using the COM-based API, but provides a much more user-friendly cover on top of it. I've found that for 99% of use cases, VBoxManage can cover it. VBoxManage also handles all error handling, does proper exit status (0 for success, non-zero for everything else), etc. After 1.5 years of the C API I've switched back to VBoxManage because its simply easier to use and does what I need to do. The downside is you must use a subprocess to talk to VBoxManage. The upside is VBoxManage changes relatively infrequently, and as such it makes it very easy to support many versions of VirtualBox.
I hope this helps!
I need to develop an iPhone/iPod Touch application that creates a server to send some data stream (characters or bytes) to a Windows C++ application via Bluetooth. I'm thinking of creating a TCP connection, but don't know where to start.
What iPhone API should I use do to something like this? Does anyone knows some code examples that i can use to do this?
And in Windows, what should I use to support this kind of communication?
Thanks
Yes. From what it looks like you can use the PAN bluetooth profile (the same profile used for tethering) with everything except the original iPhone.
Here's an article doing bluetooth over iPhone/iPad using GameKit. The article notes that you would need at least 2 iPhone/iPad devices running iPhone OS 3.0, but I wouldn't take that as an impossibility to talk to any other bluetooth capable device.
Update
This forum indicates that the iPhone is only capable of headset pairing. It could be that the iPhone is "picky" about what you can pair it with.
"The iPhone only recognizes the "headset" profile. Another well thought out idea from Apple. No A2DP profiles, no OBEX."
-sapporobaby
Update 2
As jamone as indicated iPhone 3.0 supports A2DP. How nice is that?
Here's a table listing of iPhone/iPad bluetooth supported profiles
I'm pretty sure third-party developers don't have sufficient access to the Bluetooth stack to do this via published APIs (i.e. via an app you publish to the App Store).
Is using WiFi an option? That's what most developers seem to be using for client/server communications. If that's the case, see if you can distribute Apple's Bonjour runtime with your app. If you search the developer site for Bonjour, they have code samples (though probably no Windows examples).