Skype: What sort of framework changes has Microsoft made?
Has Microsoft previously started rolling out improvements to Skype's P2P framework? As indicated by one report, Microsoft has started moving in some Microsoft-facilitated Linux boxes.
It's been one year since Microsoft declared plans to get Skype and seven months since administrative bodies endorsed the exchange, empowering Microsoft to take control formally of the VOIP seller.
As per Ars Technica, Microsoft as of now has made some noteworthy changes to the back-end Skype foundation, "supplanting distributed customer machines with a huge number of Linux boxes that have been solidified against the most widely recognized sorts of hack assaults." Ars is constructing the report in light of a security specialist's discoveries; he guarantees the change happened two months prior.
I thought about a year ago whether and when Microsoft would put its stamp on Skype's back-end frameworks. With earlier acquisitions, Microsoft at times gives recently gained organizations a chance to keep on running a similar equipment, programming and administrations they've been utilizing before a Redmond assume control. Generally, after some time, be that as it may, Microsoft will in general attempt to adjust the foundation of organizations they gain with whatever is left of the servers driving the organization's different specialty units.
Hotmail is an exemplary model. The Hotmail servers were pursuing FreeBSD for quite a long time Microsoft started endeavoring to move them to Windows 2000.
Not long after Microsoft obtained Skype, I inquired as to whether and when Microsoft intended to change Skype's framework and improvement procedures. It was evident from the Microsoft Jobs postings that Skype was utilizing bunches of PHP, Perl, Python and open-source. Would it ever bode well, for instance, to move any Skype administrations to Azure? Or on the other hand to attempt to change over Skype into a .Net shop?
I was let it know was too soon to state.
In July 2011, Skype executives said they were purchasing up some sort of servers for their datacenters to help keep up transmission capacity for Skyping by means of Facebook, however they never determined which working frameworks they were running.
I asked again today whether the Softies would remark on the most recent write about changes returning to Skype's end foundation. Up until now, no reaction.
Refresh: Via a Microsoft representative comes a reaction which appears to me to substantiate Ars' report (in any event to a limited extent):
"As a feature of our progressing duty to persistently enhance the Skype client encounter, we created supernodes which can be situated on devoted servers inside secure datacentres. This has not changed the basic idea of Skype's shared (P2P) design, in which supernodes essentially enable clients to discover each other (calls don't go through supernodes). We trust this methodology has quick execution, adaptability and accessibility benefits for the a huge number of clients that make up the Skype people group," as per Mark Gillett, Corporate Vice President, Skype Product Engineering and Operations.
Microsoft didn't react concerning whether these supernodes are currently Microsoft-facilitated Linux servers. Organization authorities additionally didn't react to my inquiry with respect to when the adjustment in foundation happened.
A speedy inquiry on the Microsoft Jobs sheets demonstrates that Skype is still essentially a PHP, Perl and Python shop. One open Skype work indicated that either Linux or Windows experience would be satisfactory.
It's been one year since Microsoft declared plans to get Skype and seven months since administrative bodies endorsed the exchange, empowering Microsoft to take control formally of the VOIP seller.
As per Ars Technica, Microsoft as of now has made some noteworthy changes to the back-end Skype foundation, "supplanting distributed customer machines with a huge number of Linux boxes that have been solidified against the most widely recognized sorts of hack assaults." Ars is constructing the report in light of a security specialist's discoveries; he guarantees the change happened two months prior.
I thought about a year ago whether and when Microsoft would put its stamp on Skype's back-end frameworks. With earlier acquisitions, Microsoft at times gives recently gained organizations a chance to keep on running a similar equipment, programming and administrations they've been utilizing before a Redmond assume control. Generally, after some time, be that as it may, Microsoft will in general attempt to adjust the foundation of organizations they gain with whatever is left of the servers driving the organization's different specialty units.
Hotmail is an exemplary model. The Hotmail servers were pursuing FreeBSD for quite a long time Microsoft started endeavoring to move them to Windows 2000.
Not long after Microsoft obtained Skype, I inquired as to whether and when Microsoft intended to change Skype's framework and improvement procedures. It was evident from the Microsoft Jobs postings that Skype was utilizing bunches of PHP, Perl, Python and open-source. Would it ever bode well, for instance, to move any Skype administrations to Azure? Or on the other hand to attempt to change over Skype into a .Net shop?
I was let it know was too soon to state.
In July 2011, Skype executives said they were purchasing up some sort of servers for their datacenters to help keep up transmission capacity for Skyping by means of Facebook, however they never determined which working frameworks they were running.
I asked again today whether the Softies would remark on the most recent write about changes returning to Skype's end foundation. Up until now, no reaction.
Refresh: Via a Microsoft representative comes a reaction which appears to me to substantiate Ars' report (in any event to a limited extent):
"As a feature of our progressing duty to persistently enhance the Skype client encounter, we created supernodes which can be situated on devoted servers inside secure datacentres. This has not changed the basic idea of Skype's shared (P2P) design, in which supernodes essentially enable clients to discover each other (calls don't go through supernodes). We trust this methodology has quick execution, adaptability and accessibility benefits for the a huge number of clients that make up the Skype people group," as per Mark Gillett, Corporate Vice President, Skype Product Engineering and Operations.
Microsoft didn't react concerning whether these supernodes are currently Microsoft-facilitated Linux servers. Organization authorities additionally didn't react to my inquiry with respect to when the adjustment in foundation happened.
A speedy inquiry on the Microsoft Jobs sheets demonstrates that Skype is still essentially a PHP, Perl and Python shop. One open Skype work indicated that either Linux or Windows experience would be satisfactory.
Nhận xét
Đăng nhận xét