[Dev] FW: Tizen 3.0 common wifi socket client-server communication

PINTU KUMAR pintu.k at samsung.com
Tue Jun 6 15:16:53 UTC 2017


Hi,

> the wifi api's would only be for configuring the wifi device/setup/connection
details.
> you still would use regular sockets anyway to send/receive data.
Thanks all. Yes we could able to communicate, send/receive data between Tizen
mobile app 2.4 and Raspberry pi 2 (with tizen 3.0 common profile).
On Tizen mobile side - we used Tizen wifi API for connection, and regular Linux
socket send/receive API.
On Raspberry pi: we only used regular Linux socket APIs
We could able to create many use cases using this communication, with some
external hardware connections.

After we complete and verify all our use cases, we will be contributing the
Tizen App on Tizen store.
However, we also want to contribute the server part under Tizen 3.0 common
profile (or other repo).
Please let us know how to contribute our code to: review.tizen.org
I already have access to view these repo, but not sure where to put it.
Please let me know how to upload.

Thanks,
Pintu

> -----Original Message-----
> From: Carsten Haitzler (The Rasterman) [mailto:tizen at rasterman.com]
> Sent: Friday, May 26, 2017 7:29 AM
> To: PINTU KUMAR
> Cc: dev at lists.tizen.org; akshit.a1 at partner.samsung.com;
> vivek.v17 at partner.samsung.com; pravin.c at samsung.com
> Subject: Re: [Dev] FW: Tizen 3.0 common wifi socket client-server
communication
> 
> On Thu, 25 May 2017 14:47:02 +0530 "PINTU KUMAR" <pintu.k at samsung.com>
> said:
> 
> > ** On behalf of Akshit & Vivek **
> >
> >
> >
> > Hello Tizen Dev team,
> >
> > I have 2 college interns in my team. They are trying to build wifi
> > client/server based socket communication using Tizen API, to
> > communication between 2 devices.
> >
> > One device contains Tizen 3.0 common (headless).
> >
> > Another device is Z2 with Tizen 2.4
> >
> > They were able to achieve this using normal TCP Linux socket APIs.
> >
> > But, they want to develop a Tizen App (using Tizen studio) on Z2,
> > using the Tizen wifi Native APIs.
> >
> > We could not the proper Wi-Fi API for send/receive data between 2 devices.
> >
> > If there is any reference or sample source code please let us know.
> 
> the wifi api's would only be for configuring the wifi device/setup/connection
details.
> you still would use regular sockets anyway to send/receive data.
> 
> you can use ecore_con or ecore_ipc (a layer on top of ecore_con that ensures
full
> ipc message packet delivery for you).
> 
> https://developer.tizen.org/development/api-references/native-
> application?redirect=https://developer.tizen.org/dev-
> guide/3.0.0/org.tizen.native.mobile.apireference/group__Ecore__Con__Group.html
> 
> https://developer.tizen.org/development/api-references/native-
> application?redirect=https://developer.tizen.org/dev-
> guide/3.0.0/org.tizen.native.mobile.apireference/group__Ecore__IPC__Group.html
> 
> this will integrate into the mainloop and make communications async. it also
will
> handle optional ssl transport encryption for you (so you don't have to do that
by
> hand with regular unix/bsd sockets). it'll also handle async dns lookups for
you. they
> both allow you to set up servers and clients 9connect to a server). but these
are just
> like your sockets code - they dont determine the connection mechanism (wifi,
> 3g/gsm/lte, bt net, usbnet, ethernet etc.).
> 
> >
> >
> >
> >
> > Thanks
> >
> >
> >
> > From: Akshit Gandhi [mailto:akshit.a1 at partner.samsung.com]
> > Sent: Thursday, May 25, 2017 12:22 PM
> > To: PINTU AGARWAL
> > Subject: [Dev] Tizen 3.0 common wifi socket client-server
> > communication
> >
> >
> >
> > Hello Everyone,
> >
> > Can anyone give me some guide/reference for making a tizen app (client
> > +server) using WiFi sockets as a communication method. I have done it
> > +using
> > Linux API's but now I want to do it with Tizen Native API's.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> 
> 
> --
> Carsten Haitzler (The Rasterman) <tizen at rasterman.com>




More information about the Dev mailing list