[TIMOB-7311] iOS: Change Ti.Network.BonjourService/BonjourBrowser to take a Ti.Network.Socket.TCP object
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2020-01-23T15:10:50.000+0000 |
Affected Version/s | Release 2.0.0 |
Fix Version/s | Release 9.0.0 |
Components | iOS |
Labels | tbs-1.9.0, training |
Reporter | Stephen Tramer |
Assignee | Christopher Williams |
Created | 2012-01-20T10:15:03.000+0000 |
Updated | 2020-01-29T16:12:13.000+0000 |
Description
In order to correctly deprecate (and remove)
Ti.Network.TCPSocket
which has been deprecated since the introduction of better sockets in 1.7.0, without disrupting the ability to use these features, the Bonjour code needs to be updated to take Ti.Network.Socket.TCP
objects. This should not be a difficult task, although we will need to make developers aware of the change prior to release.
This ticket should be resolved at the same time as TIMOB-4662.
Almost 1 year... still no solution?
There has been (so far) very little demand for this change which is why it has not been prioritized higher. Is there a reason you need this?
The reason is simple and pretty straight forward. Without a fix, I don't see how Ti.Network.BonjourService can work. Titanium.Network.BonjourService.publish() take a Titanium.Network.TCPSocket as a parameter, which has been dropped a while ago and replaced by Titanium.Network.Socket.TCP Titanium.Network.BonjourService is totally dead/not functional without that fix. It's impossible to publish a service through that way. It needs to be updated to handle Titanium.Network.Socket.TCP for his publish() method. Otherwise it's pointless to keep that framework in that state in Titanium SDK. So I see different scenario: 1. Leave it like this forever and/or drop the entire BonjourService and BonjourBrowser 2. Do that fix in order to handle Titanium.Network.Socket.TCP 3. Suggest a work around or an alternative to publish BonjourServices through Titanium (3rd part module or else)
This was fixed at the same time as TIMOB-27619 and TIMOB-27076
Ticket closed. As Chris has mentioned, we have resolved this ticket via the above 2 tickets.