File transfer via bluetooth programatically

  • Thread starter Thread starter Jon Hopper
  • Start date Start date
J

Jon Hopper

I have 2 PDA's both with Bluetooth. I am attempting to programmatically
connect to the second PDA from the first via Bluetooth, and then transfer
files from one to the other after renaming the file, using the first as a
master.

Is there any way this can be done using the .net framework?
 
What level of user interaction do you want (or not want) in the process. One
of the simplest ways is to invoke the built in irsquirt / beam application
to begin sending a file. Alternatively you can go down the route of writing
your own file sending and receiving service and implement a sender and
listener on each device. How you do this will also depend on the Bluetooth
stack on your devices since the two main ones - Microsoft and Broadcom
(Widcomm) are programatically very different. For a hybrid solution it's
possible to send data conforming to the Obex Push Profile so that the file
can be received on another device without any custom software - See the
example here:-
http://www.gatefold.co.uk/obex/
The latest OpenNETCF.Net.Bluetooth (for devices with Microsoft Stack) is
here:-
http://www.peterfoot.net/BluetoothLibraryMarchEdition.aspx

Peter
 
I want the user to have a little interaction as possible.

I want to display a list of files located on the second PDA on the first
PDA. Then when I select the file to rename the file and transfer the file to
the first PDA.

I think have the Broadcom (Widcomm) stacks on the PDA's
 
Any sort of file transfer requires that both ends of the connection
cooperate. If that wasn't the case, the virus writers would completely
control your computer in about 30 seconds. If you have wireless networking
(or any sort of networking, for that matter), and if the other end of the
connection boasts an FTP server, HTTP server, or file sharing, you may be
able to use one of those methods to transfer files. You are the only one
who will know what is possible, though. We can't see the devices and don't
know anything about the networking structure where they operate.

Paul T.
 
the structure is several users using a PDA each and a team leader who
collects all of the results from each user's PDA.

So we have a min of 2 PDA's. A master and a slave.
both devices can have performed the handshake first, so that they are
comminicating before any interaction takes place,
 
You might be able to do this effectively with WiFi, yes. Is there any WiFi
infrastructure (access points), or are the devices only going to ever
communicate peer-to-peer? If there's infrastructure, you configure the
devices for infrastructure mode; otherwise, ad hoc mode. On top of that,
you'd build your application and, presumably, use TCP as the communication
base. When the master PDA comes on, the master program opens a socket and
waits for clients to connect. When the slave device is ready to update the
master, it connects and, once connected, sends whatever it wants over the
TCP connection. When done, it breaks the connection.

Paul T.
 
Back
Top