Skip to content

Great blog post about App Tethering by Steffen Nyeland

App Tethering is a new capability in XE6. RTL components are included for connecting your VCL and FMX apps together on the same machines or multi-devices in your Object Pascal and C++ projects. XE6 includes the TTetheringManager and TTetheringAppProfile components for your use. Using app tethering (from the Embarcadero DocWiki), your applications can easily:

  • Discover other applications that are using app tethering, running either on the same device as your application or on other connected devices.
  • Run actions remotely. An application can publish actions using app tethering. Then other applications can remotely invoke any of these actions on the former application.
  • Share data between applications. App tethering allows sharing of standard data types and streams.

The app tethering feature does not depend on a specific transport or protocol, and new protocols can be implemented using the app tethering API. The RTL provides built-in support for Ethernet connections between applications on the same local areal network (LAN), including applications running on the same device. Bluetooth support for App Tethering is on our roadmap for a future release.

Steffen Nyeland has written a great blog post showing how to use a barcode scanning app on Android and iOS and send the data to a desktop app. Check out the blog post at  http://fixedbycode.blogspot.dk/2014/04/fun-with-delphi-xe6-app-tethering-and.html. Steffen also has links to download the sender and receiver apps. He also includes links to additional sources of information.

Thank you Steffen and keep up the great work!

{ 4 } Comments

  1. Joseph | April 22, 2014 at 10:16 pm | Permalink

    Mr. Intersimone, I was very disappointed to find that (as is all to common) the app tethering is virtually undocumented on EMBT’s website. The paragraph you quoted that contains "app tethering API" is from the website and when one clicks on the app tethering API link one gets to a page where almost every link from there gives the dreaded "no information available" notice.

    It seems despite promises of QPS Delphi continues to ship without adequate written documentation. :-( Is technical documentation a "volunteer" position like the QC website? How did EMBT write the existing TCP protocol for app tethering if there was no documentation?

    The last Delphi book (at least in the US) from a commercial publisher came out in 2005. High quality documentation is more important now than ever. It doesn’t matter how good or stable or bug-free a new Delphi feature is if no one knows how to use it. I don’t think waiting weeks or months hoping MVPs will figure out how it works and make a blog post for the rest of us somewhere is good enough.

  2. Marco Cantu | April 23, 2014 at 2:20 am | Permalink

    Joseph, thanks for your input. We know that when some features are completed at the end of the development cycle, their documentation will be thin. While the API documentation for tethering is very limited, the tutorials explaining how to set up and configure your application (see links above) are fairly detailed. We also ship several demos, and more will come.

    Speaking of books, separating "commercial" publishers from "self-publishing" seems quite unfair to me. There have been few Delphi books in recent years, but there have been quite a few remarkable ones.

  3. Andre | April 25, 2014 at 1:22 am | Permalink

    Quote from Marcu Cantu:

    "We know that when some features are completed at the end of the development cycle, their documentation will be thin."

    You have forgotten to mention that also testing is very thin if not completly ignored, or you just let your customers test it out in production…

    So, could you and Mr. Intersimone please explain how that huge bug could slip in App Thethering (see QC #124114, and more) without anyone from Emb Dev und Q&A-Team noticed it?

    Only from looking at the source the source for a minute or so and seeing that magic string constants, it was the first thing which come to mind what should be testet. And that test showed it breaks it.

    So we have to assume that Emb did not do any real testing. Just pushing out some unfinished and buggy feature.

  4. android | August 16, 2014 at 8:59 am | Permalink

    Your style is unique compared to other folks I’ve read stuff from.
    Thank you for posting when you have the opportunity, Guess I’ll just bookmark this page.

Post a Comment

Your email is never published nor shared. Required fields are marked *

Bad Behavior has blocked 4 access attempts in the last 7 days.

Close