Documentation. Draft 1. Apr 22

[Hussain]

Here's the 1st draft.

Anupam has been devoting a lot of time on this documentation. Big thanks to him.

I've filled in the remaining section names. Need volunteers to work on them.

Let me know where you make changes.

TIA

[Mike Petrichenko]

Good time of the day!

WOW! You did the Great Job! Thank you A LOT!!!

[Hussain]

More sections have been updated.

[AnupamVarghese]

Mike, you need to verify if some of the things we are writing is 100% correct  . Since many of the things only you will know best  . Maybe you could have a 'Verified' tag that you could put on sections that you have checked? Hussain what say?

[Mike Petrichenko]

I am already doing it

Here is requested Vendor IDs

Code   Company
0   Ericsson Technology Licensing
1   Nokia Mobile Phones
2   Intel Corp.
3   IBM Corp.
4   Toshiba Corp.
5   3Com
6   Microsoft
7   Lucent
8   Motorola
9   Infineon Technologies AG
10   Cambridge Silicon Radio
11   Silicon Wave
12   Digianswer A/S
13   Texas Instruments Inc.
14   Parthus Technologies Inc.
15   Broadcom Corporation
16   Mitel Semiconductor
17   Widcomm, Inc.
18   Zeevo, Inc.
19   Atmel Corporation
20   Mitsubishi Electric Corporation
21   RTX Telecom A/S
22   KC Technology Inc.
23   Newlogic
24   Transilica, Inc.
25   Rohde & Schwarz GmbH & Co. KG
26   TTPCom Limited
27   Signia Technologies, Inc.
28   Conexant Systems Inc.
29   Qualcomm
30   Inventel
31   AVM Berlin
32   BandSpeed, Inc.
33   Mansella Ltd
34   NEC Corporation
35   WavePlus Technology Co., Ltd.
36   Alcatel
37   Philips Semiconductors
38   C Technologies
39   Open Interface
40   R F Micro Devices
41   Hitachi Ltd
42   Symbol Technologies, Inc.
43   Tenovis
44   Macronix International Co. Ltd.
45   GCT Semiconductor
46   Norwood Systems
47   MewTel Technology Inc.
48   ST Microelectronics
49   Synopsys
50   Red-M (Communications) Ltd
51   Commil Ltd
52   Computer Access Technology Corporation (CATC)
53   Eclipse (HQ Espana) S.L.
54   Renesas Technology Corp.
55   Mobilian Corporation
56   Terax
57   Integrated System Solution Corp.
58   Matsushita Electric Industrial Co., Ltd.
59   Gennum Corporation
60   Research In Motion
61   IPextreme, Inc.
62   Systems and Chips, Inc
63   Bluetooth SIG, Inc
64   Seiko Epson Corporation
65   Integrated Silicon Solution Taiwan, Inc.
66   CONWISE Technology Corporation Ltd
67   PARROT SA
68   Socket Communications
69   Atheros Communications, Inc.
70   MediaTek, Inc.
71   Bluegiga (tentative)
72   Marvell Technology Group Ltd.
65535   For use in internal and interoperability tests before a Company ID has been assigned. May not be used in products. Only used in Link Manager testing.

[Hussain]

Anupam

Definitely. That is implicit. There is no way for the documentation to be accurate unless Mike checks it. I don't know if he has the time to read everything.

Mike:
1. I hope you have the time to read it
2. If you make changes to the API's (method / property / parameter names) that would have to go into the document

Others: Please, we need more people to volunteer for this.

[Mike Petrichenko]

Good time of the day!

I will read document ASAP and add comments.

Thank you a lot!!!!

[Mike Petrichenko]

Here is short notice about GSMModem and services:
Usually GSM phones provide the same functionality for DUN as for SerialPort.
For example Siemens. It has 3 services:
DUN
SerialPort
HandsFree
DUN and SerialPort has he same port just different names.
HandsFree has the other port number but can works as GSM modem as well.
Some other devices can do the same.

P.S. I am really do nt know the good way how to detect real needed service to use. So if you have some ideas - I am ready to implement that.

[AnupamVarghese]

IMHO,
1. DUN was created just for the Internet function, HandsFree for Human Interface, while SPP was for everything 'modem' like.
2. SPP is more widely deployed than DUN or HandsFree.

So I think, my first preference would always be SPP.
If I have to do anything with Internet Connectivity, i'll use DUN.

I donno if my assumptions are correct, but I guess they are. Also, what happens when you use another transport like IrDA? Isn't SPP the only universal thing then?

Also, I'm still not getting OnNew over IrDA, which I will post in the correct forum topic.

[Mike Petrichenko]

Few comments added.

[Hussain]

Mike

Thanks. Have incorporated the comments.

I don't understand one of your comments:

Incoming Authentication requests can be handled only for MS Bluetooth API.
Outgoing authentication can be handled for any APIs BUT only for MS it actually HANDLER. For other APIs it internally call Pair method.

Does that mean that the Authenticator only works with MS stack? What happens if I try to create a connection using Widcomm and the device wants to authenticate?

You say it will call the 'Pair' method. Would I still get OnPinRequest event for the Authenticator object?

[Mike Petrichenko]

Good time of the day!

Yes. I will call OnPINRequest event. But for MS API it do the OS for you but for other APIs it is internal call. I mean that drivers do not ntify high-level applications about authentication requests. Only MS API can do that.

[Mike Petrichenko]

BTFX 5.2.1
BFObjectPushClient
new method: PutStream(Data as BFByteArrayX)

Sends data stream to the target device wrapping data into OBEX packets.

[Mike Petrichenko]

BTFX 5.2.1
BFObjectPushServer
new event: OnObjectStream(Data as BFByteArrayX, Name as String)

Passes received data (file) as a byte array.

[AnupamVarghese]

Is there any advantage on sending a file as a stream compared to a normal send?