We are just testing Beta.3 and socket server functionality and cross domain files. but have some problems.
We have made a financial application in Adobe Flex, and we are thinking of porting this to Silverlight, now that it is becomming mature and with a set of controls.
A problem though, our Streamserver runs on port 80, which the silverlight app. must connect to (since many banks does not have other ports than this open)
The Streamserver also sends out a cross-domain file.:
The first think that happens when you connect, is that the streamserver sends out a cross-domain file giving access to port 80. But not in SIlverlight so far. :-(
Silverlight applications can only connect to sockets in the range 4502-4532. You cannot use port 80 for your application. There's a somewhat heated conversation on this topic here:
http://silverlight.net/forums/p/81467/192712.aspx
No reason for us to even consider porting to Silverlight parallelly with our Flex application. It would be a completely no-go not to use port 80 to access the stream. Much people would use our application during work hours, beeing at work, and other ports
that web, FTP, STMP will be closed.
Too-bad, we could have used the multi-thread capability of Silverlight which is not present in Flex.
But it is simply not an option for us to start modifying our serverbase, this is standard socket servers, that has 3 different clients connected. We want to use standards that are not bound to OS´ses. So doing a WCF service, that is not released yet is not
a viable option
We just hope that Msft realized that is is not neessary to make stricter restrictions that the one Adobe has imposed throught their Domain policies.
Hi Lars, The lack of arbitrary socket ports is indeed silly. But even with Flash or even if SilverLight did support sockets over 80, you still need to support connections over HTTP. Some corporations behind proxies simply do not permit socket connections
and you must go thru the proxy.
Here's a note for you: Flash in Internet Explorer has a problem with version detection. This is noted as Flash suddenly stops working in IE. It's not flash that has stopped working, it is the version detection that has stopped working.... Your site failed
in IE because of it... saying you must install flash etc...
The version detection occurs in AC_RunActiveContent.js. You can read about my solution for the problem here:
lars67
Member
4 Points
8 Posts
Socket Server
Mar 22, 2009 02:13 PM | LINK
We are just testing Beta.3 and socket server functionality and cross domain files. but have some problems.
We have made a financial application in Adobe Flex, and we are thinking of porting this to Silverlight, now that it is becomming mature and with a set of controls.
A problem though, our Streamserver runs on port 80, which the silverlight app. must connect to (since many banks does not have other ports than this open)
The Streamserver also sends out a cross-domain file.:
This doesn´t work. Any ideas? The documentation on the .NET is very confusion and of various qualityThanks in advanceCrossdomain Socket TCP
lars67
Member
4 Points
8 Posts
Re: Socket Server
Mar 22, 2009 02:17 PM | LINK
For those interested This is the application in question:
http://www.softcapital.com/radarlite
The first think that happens when you connect, is that the streamserver sends out a cross-domain file giving access to port 80. But not in SIlverlight so far. :-(
andulvar
Member
181 Points
129 Posts
Re: Socket Server
Mar 22, 2009 04:12 PM | LINK
Silverlight applications can only connect to sockets in the range 4502-4532. You cannot use port 80 for your application. There's a somewhat heated conversation on this topic here: http://silverlight.net/forums/p/81467/192712.aspx
lars67
Member
4 Points
8 Posts
Re: Re: Socket Server
Mar 22, 2009 04:25 PM | LINK
Shit [:(]
No reason for us to even consider porting to Silverlight parallelly with our Flex application. It would be a completely no-go not to use port 80 to access the stream. Much people would use our application during work hours, beeing at work, and other ports that web, FTP, STMP will be closed.
Too-bad, we could have used the multi-thread capability of Silverlight which is not present in Flex.
codeblock
Contributor
4070 Points
716 Posts
Re: Re: Re: Socket Server
Mar 22, 2009 05:07 PM | LINK
If you need to use sockets ther is nothing to do.
But if you can change your transport you may consider the usage of a webservice.
But if you are talking about streams probably this is not your case.
What are you streaming?
--
Andrea Boschin
MVP Silverlight & Silverlight Insider
Silverlight Playground, Me on Twitter
lars67
Member
4 Points
8 Posts
Re: Re: Re: Socket Server
Mar 23, 2009 05:31 AM | LINK
Hello Andrea
We are streaming stockquotes from a socket server.
codeblock
Contributor
4070 Points
716 Posts
Re: Re: Re: Re: Socket Server
Mar 23, 2009 07:56 AM | LINK
Have you seen the PollingDuplex
http://petermcg.wordpress.com/2008/09/03/silverlight-polling-duplex-part-1-architecture/
HTH
--
Andrea Boschin
MVP Silverlight & Silverlight Insider
Silverlight Playground, Me on Twitter
davidezordan
Contributor
6294 Points
957 Posts
Re: Re: Re: Re: Re: Socket Server
Mar 23, 2009 03:10 PM | LINK
Hi,
I've posted an updated example of Duplex support in SL3 here: http://www.davidezordan.net/blog/?p=935
Hope this helps.
Silverlight MVP
Blog Twitter Silverlight Experts
lars67
Member
4 Points
8 Posts
Re: Re: Re: Re: Re: Socket Server
Mar 30, 2009 06:57 AM | LINK
Hi
Thanks for your suggestions. [:)]
But it is simply not an option for us to start modifying our serverbase, this is standard socket servers, that has 3 different clients connected. We want to use standards that are not bound to OS´ses. So doing a WCF service, that is not released yet is not a viable option
We just hope that Msft realized that is is not neessary to make stricter restrictions that the one Adobe has imposed throught their Domain policies.
Socket policy
DonMoir
Member
8 Points
4 Posts
Re: Re: Re: Re: Re: Socket Server
Apr 01, 2009 11:44 AM | LINK
Hi Lars, The lack of arbitrary socket ports is indeed silly. But even with Flash or even if SilverLight did support sockets over 80, you still need to support connections over HTTP. Some corporations behind proxies simply do not permit socket connections and you must go thru the proxy.
Here's a note for you: Flash in Internet Explorer has a problem with version detection. This is noted as Flash suddenly stops working in IE. It's not flash that has stopped working, it is the version detection that has stopped working.... Your site failed in IE because of it... saying you must install flash etc...
The version detection occurs in AC_RunActiveContent.js. You can read about my solution for the problem here:
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=72&catid=675&threadid=1436087&enterthread=y
Here is my own version of socket and HTTP connection support in the form of a Real Time Blog:
http://sms.pangolin.com/rtblog/
Don