Thanks Jonas
You're raising a very interesting point here
I'd love to see <img src="ws://...." event="foo" > support for which each
event: foo
data: image/png;base64, <some base64 encoded image>
would update the image
we might also imagine that any input field could accept source and event attributes and then have
<input type="text" source="ws://..." event="foo" >
which value would be updated live with the data content fo each matching event flag
we could imagine similar behaviors with tcp or udp messages
<pre source="udp://..." ></pre>
could be used to show log messages (could also work with "ws://..")
On 2 juil. 2013, at 22:42, Jonas Sicking wrote:
On Thu, Jun 27, 2013 at 8:47 AM, Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com<mailto:Claes1.Nilsson@sonymobile.com>> wrote:
address + port vs uri, https://github.com/sysapps/raw-sockets/issues/17:
I think we need more discussion on this proposal. Personally I need to get a better view on advantages/disadvantages of using URI addresses instead of explicit IP-address and port arguments.
I would recommend reaching out to IANA on this, and possibly the W3C webapps working group.
In general on the web platform, any URI can be used anywhere URIs can be used. So a blob: or a filesystem: URI works in <img src="..."> as well <iframe src="..."> and XMLHttpRequest.open("GET", "...").
That wouldn't be the case with a tcp: scheme or a udp: scheme.
However, it's also not the case with ws: or wss:. In fact, tcp: and udp: work pretty similarly to ws: and wss:.
Generally I don't have a strong opinion, but minting new schemes tend to be a pretty political thing that you generally want to stay away from. But it might be the right thing to do.
/ Jonas
[cid:fd4f7a.png@71d6b922.43b2bdfd]
Alexandre Morgaut
Wakanda Community Manager
Email : Alexandre.Morgaut@4d.com<mailto:Alexandre.Morgaut@4d.com>
Web : www.4D.com<http://www.4D.com>
4D SAS
60, rue d'Alsace
92110 Clichy - France
Standard : +33 1 40 87 92 00
[cid:8754ad.png@4765c05f.4a98b03f]<http://www.4d.com/fr/company/events/summiteu2013.html>
