I am using win32 sockets to develop a Bluetooth application. But I see that on the msdn they have:
•Bluetooth and WSALookupServiceBegin for Device Inquiry
•Bluetooth and WSALookupServiceBegin for Service Discovery
What is this service discovery? I mean if I have a Bluetooth device it should provide Bluetooth serivce right? Or am I confusing things here?
Could someone please explain this?
I would like to get a good understanding before starting any kind of coding :)
What is this service discovery? I mean if I have a Bluetooth device it should provide Bluetooth serivce right?
Yes. In order to use Bluetooth technology, a device must be compatible with the subset of Bluetooth profiles necessary to use the desired services.
Think of it as IP and Port numbers. While you need the IP (Bluetooth device) to connect to a host, you still need the Port (Bluetooth service) in order to connect and use the host. A Bluetooth service will tell you the capability of the device and what it can do.
Related
I have an issue where WiFi is not available on an Android device. We want to stream image data from the device using a websocket server (written using WebSocket++) through to the PC. However, I'm not sure if this is possible without operational WiFi. So, the position we are in is that we may only have the USB link available.
Someone today suggested we might be able to get Websockets working using adb port forwarding (see https://developer.android.com/studio/command-line/adb#forwardports), but I'm not sure if that's correct. Could this work, and what would that solution look like?
Are there any other reasonable options. I'm not certain if tethering is available on the device and if that could be another solution?
First allow me to say that I don't have any experience developing drivers for OSX, nor drivers for Windows. So, there are a lot of things that I don't understand about how drivers work; I'm sure it'll be evident in my question.
I have a modem that is able to open and close TCP/UDP sockets using AT commands. I would like to create some kind of program (kernel extension? driver?) that implements a network driver, converting the network interface calls into AT command serial messages.
That's the basic jist of it. I'm essentially asking if anybody can point me in the right direction / give me a high level overview of how they would approach it and what Apple guides to focus on.
The XNU networking stack -- like most network stacks -- expects network devices to send and receive IP packets directly. It isn't tooled to work with network devices that handle part of the network stack (like TCP or UDP) internally -- it won't be possible to implement a network driver which uses this device.
You might have more luck exposing this device as a SOCKS proxy. You will need to write a userspace daemon which listens on a TCP port on localhost (on the computer) and relays traffic to the serial device; once that's done, you can set the computer to use that device as a SOCKS proxy in the Networking control panel.
(As an aside: most devices that implement this type of interface have a very low limit on the number of open sockets -- often fewer than 10. They're unlikely to be able to handle the network load generated by a desktop OS.)
I am trying to connect two windows phone emulators without router to form p2p network, is there any solution to connect them with access point without router and internet. and can be a possibility of using IP address of emulator.
answer plz
To the best of my knowledge no it is not possible in Mango - but is in WP8. You could however use a wireless network to perform create a UDP multicast socket and and then "connect" to one another that way.
Have a look at http://blogs.msdn.com/b/davrous/archive/2010/03/29/windows-phone-7-platformer-starter-kit-for-xna-studio-4-0.aspx it's got some pretty good pointers.
Is it possible to know the IPAddress of Windows Phone [Mango] devices when connected to PC through USB tethering.?
I am asking this because when i connect my phone to pc, using sockets it can connect to ANY Ipaddress. In other words, the SocketError enumeration always return me Success. which is quite strange.
If someone help me clarifying this issue.
Thanx
The phone itself can be accessed via the loopback interface (aka 127.0.0.1) - you can see that if you try to analyze the network traffic for a debug session. The level of access, however, is limited to the extent of the debugger integration.
While the phone is connected it gets the IP address 192.168.55.101. The network interface of the computer (e.g. to connect to it from the phone) has the address 192.168.55.100.
So I have a bluetooth device, this device uses SPP to transfer data between the PC and itself. It connects fine through Windows as a bluetooth device. I can find it, enter the paring code and assign it to a COM port. Now I want to be able to send data through the com port using Windows API but it is refusing to do so.
I suspect that I need to setup the COMMCONFIG Structure correctly (see below)
http://msdn.microsoft.com/en-us/library/aa363188(VS.85).aspx
Unfortunately I have no idea what is the proper setting. I know SPP is supposed to emulate the RS-232 communication... so maybe I have to study up on that to figure out the right setting? Or is there some automatic way to set the COMMCONFIG structure.
I seriously doubt it. If it would be used then you'll have no chance at guessing at the custom provider data without docs from the driver author. Pay attention to the handshake signals, serial port devices routinely ignore anything sent to them when the DTR signal is turned off. And not send anything back with DTR off. A driver would emulate that. Use EscapeCommFunction() to turn them on. Also try a serial comm program like HyperTerminal or Putty to test this so you can isolate the source of the problem.
Why not use the Bluetooth sockets API? No need for troublesome (virtual) COM ports then.
If you're using managed code then see my library 32feet.NET
If using native code, use SOCKADDR_BTH with Winsock connect etc, see e.g. Bluetooth and connect (Windows) Then you can use the standard Winsock send/recv API
Ok, I found that you can use the
GetCommConfig and GetCommState functions to figure out the settings.