<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>L2CAP support on the S140 softdevice</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22754/l2cap-support-on-the-s140-softdevice</link><description>Hi 
 From s140_nrf52840_5.0.0-3.alpha_migration-document, it is mentioned that the L2CAP API has been completely removed. Are there plans to re-expose the API? We have exposed L2CAP functionality in our app for the nrf52832 and want to see if we&amp;#39;ll be</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Jun 2017 23:44:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22754/l2cap-support-on-the-s140-softdevice" /><item><title>RE: L2CAP support on the S140 softdevice</title><link>https://devzone.nordicsemi.com/thread/89456?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2017 23:44:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6ad4447-463a-478d-86a7-35b275b993b6</guid><dc:creator>Ulrich Myhre</dc:creator><description>&lt;p&gt;The L2Cap API was a proprietary feature that made use of an under-utilized channel range for data transfers. Since the Bluetooth spec introduced the &amp;quot;Connection Oriented Channels&amp;quot; feature, this proprietary feature can be fully replaced with the formal version. It is largely the same thing, but has some key differences:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;There is an initial setup of the channel, where maximum logical and physical packet sizes are agreed upon.&lt;/li&gt;
&lt;li&gt;There is a flow control system using credits. It can largely be overridden if you handle the flow control yourself.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The proprietary feature was kept until it had a proper implementation that could replace it. Connection Oriented Channels is already included in the &lt;strong&gt;S132&lt;/strong&gt; 5.0.0-3.alpha, but I do not know if/when it will go into the S140.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>