Applets and MulticastSocket
Just curious. From the following thread....
http://forum.java.sun.com/thread.jspa?threadID=746385&tstart=0
I checked the docs ( http://java.sun.com/j2se/1.5.0/docs/api/java/net/MulticastSocket.html) and it definitely says...
Currently applets are not allowed to use multicast sockets.
Anyone know why an applet absolutely can not use that? Absolutely in the sense that that is just referring to something like the normal security restrictions that applets are under?
[523 byte] By [
jschella] at [2007-10-2 22:53:29]
> At a guess it's to be symmetrical with the
> restriction that over TCP an applet can only
> communicate with its host. Allowing multicast UDP
> would widen this.
But that is a security restriction. If the restriction is lowered then an applet could, for example, create a socket to another host right?
If that's what the javadoc said, and if there was a permission you could grant, but it isn't and there ain't so there we are I suppose. 'Currently' has been there for about ten years.
ejpa at 2007-7-14 6:07:38 >
> If that's what the javadoc said, and if there was a
> permission you could grant, but it isn't and there
> ain't so there we are I suppose. 'Currently' has been
> there for about ten years.
To clarify a normal applet will not allow one to use a Socket to another host.
I thought that there was a permission flag that could be set to allow an applet to create a Socket to another host?
If that is true then I would expect that it is possible that the same permission would allow Multicase to work.
Presuming if there is such a permission you are saying that it will not work for Multicast or that your guess would be that it won't?
I'm saying that the documentation doesn't say anything about permissions, and that I can't see a MulticastSocketPermission or anything in a SocketPermission that would support such a permission, so the presumption has to be that it's a hard-wired restriction.
ejpa at 2007-7-14 6:07:38 >
> I'm saying that the documentation doesn't say
> anything about permissions, and that I can't see a
> MulticastSocketPermission or anything in a
> SocketPermission that would support such a
> permission, so the presumption has to be that it's a
> hard-wired restriction.
Ok.
