you don't have scrum - the scrum master's role is to help the team apply scrum. yours isn't doing that, he's being the usual "pretty bad project manager", pushing the development team around reactively when he'd be better off leaving the scrum team to plan their stories, while he greases the wheels between the devteam and the organisation/client.
I'm not a sysadmin, but I don't think this is particularly significant.
1. For this type of "incoming" connection to be created, the target machine has to first bounce a packet off its own NAT. So this isn't much different from creating a new outgoing connection since it can't be entirely remote initiated.
2. Since you are already allowing outgoing connections to untrusted hosts you are at already risk, as any connection can be exploited once it is open.
So in the scenario described there wasn't much security in the first place. To consider yourself realsonably firewalled you need to block both incoming and outgoing connections and keep a close eye on any "allowed" services. (ie, use a web proxy)
I've looked at using the XMLHTTP object a couple of times in the past, and noted that this is partly how Google Suggest works.
XMLHTTP is a COM object included with recent versions of Internet Explorer. You can call it from client side JavaScript in a web page. The object will make a request to the URL you specify, and return the result into either a string variable, or an MSXML DOM object. You can then have the javascript output the results to an object (eg, a div tag) on the page without doing a full page reload.
I wrote a small tech demo that implemented a virtual tree - so when you expand a branch in the tree the client only retrieved the data it needed. This was borrowed from the approach the MSDN web site uses. The advantages to it are that it doesn't download the same data over and over like when you expand a branch in a server side tree. You also don't have to do any work at all to remember the state of the tree since there's no full page refreshes involved.
Google Suggest is similar in that it is a virtual list rather than a virtual tree. A virtual list allows you to list lots of items and jump around in the list without needing to download the entire data set when the page was loaded.
Another use for this would be dynamic forms - forms that alter the state of controls based on selections the user made in previous controls.
The biggest suprise to me was that Google have implemented this on a site live to the public. In using XMLHTTP I found it a little bit prone to locking up the browser when waiting for responses to requests. Additionally it's Windows only, so could never have been implemented on an external web site.
I'll be looking with interest at the Mozilla side of Google's implementation, since I didn't think an equivalent existed until now. Two different implementations of the same functionality is still going put a damper on the technology though.. different code for different browsers is usually more trouble than its worth.
This site collects customer feedback ratings for UK hardware suppliers. It is useful to find out about other customers experiences with a supplier should anything go wrong.
The vendor offering the cheapest prices may also be the least helpful for you in the event of a problem.
I believe the change from x86 numbers to proper names was also fueled by the change in Intels customers in recent years.
In the 70s and 80s the majority of Intels processors were bought by computer manufacturers, rather than the public, and they were seen as the primary customer base. These people were used to dealing with electronic components by quoting only a part number, so there was no reason to give the chips real names.
Intel also knew that there were a lot of companies in silicon valley that had no products ready to produce, but wanted to stir up interest in themselves and so announced product specifications before they were available. Intel refused to give their processors funky names on the grounds that if they were not careful, people may refuse to believe they existed.:)
They realised in the nineties that they could make a lot of money from selling processors to the public as upgrades, and that although their processors were used in a huge percentage of the worlds computers, most people had no idea who Intel were. So they did two things. They launched the campaign called "Intel Inside", in which they gave manufacturers discounts if they put an Intel logo on the outsides of their machines, and they gave their next major product a real name, the Pentium.
Slashdot Mirror
Still, various institutions adopted the word cyber in reference to "digital wrongdoings". Oxford dictionary made a post about it.
you don't have scrum - the scrum master's role is to help the team apply scrum. yours isn't doing that, he's being the usual "pretty bad project manager", pushing the development team around reactively when he'd be better off leaving the scrum team to plan their stories, while he greases the wheels between the devteam and the organisation/client.
Each CMS has different benefits. You have to figure out what's important for you and pick the closest fit for your requirements. Use a decision table.
I'm not a sysadmin, but I don't think this is particularly significant.
1. For this type of "incoming" connection to be created, the target machine has to first bounce a packet off its own NAT. So this isn't much different from creating a new outgoing connection since it can't be entirely remote initiated.
2. Since you are already allowing outgoing connections to untrusted hosts you are at already risk, as any connection can be exploited once it is open.
So in the scenario described there wasn't much security in the first place. To consider yourself realsonably firewalled you need to block both incoming and outgoing connections and keep a close eye on any "allowed" services. (ie, use a web proxy)
They're not UK sockets. Refer to this handy socket identification page.
http://users.pandora.be/worldstandards/electricit
I've looked at using the XMLHTTP object a couple of times in the past, and noted that this is partly how Google Suggest works.
XMLHTTP is a COM object included with recent versions of Internet Explorer. You can call it from client side JavaScript in a web page. The object will make a request to the URL you specify, and return the result into either a string variable, or an MSXML DOM object. You can then have the javascript output the results to an object (eg, a div tag) on the page without doing a full page reload.
I wrote a small tech demo that implemented a virtual tree - so when you expand a branch in the tree the client only retrieved the data it needed. This was borrowed from the approach the MSDN web site uses. The advantages to it are that it doesn't download the same data over and over like when you expand a branch in a server side tree. You also don't have to do any work at all to remember the state of the tree since there's no full page refreshes involved.
Google Suggest is similar in that it is a virtual list rather than a virtual tree. A virtual list allows you to list lots of items and jump around in the list without needing to download the entire data set when the page was loaded.
Another use for this would be dynamic forms - forms that alter the state of controls based on selections the user made in previous controls.
The biggest suprise to me was that Google have implemented this on a site live to the public. In using XMLHTTP I found it a little bit prone to locking up the browser when waiting for responses to requests. Additionally it's Windows only, so could never have been implemented on an external web site.
I'll be looking with interest at the Mozilla side of Google's implementation, since I didn't think an equivalent existed until now. Two different implementations of the same functionality is still going put a damper on the technology though.. different code for different browsers is usually more trouble than its worth.
You have it in your PCs and disk drives.
All I see in my disk drive is dust.
Ah, wait a minute. You must be right.
Congratulations to Adidas for inventing the first shoe you can boot.
This site collects customer feedback ratings for UK hardware suppliers. It is useful to find out about other customers experiences with a supplier should anything go wrong.
The vendor offering the cheapest prices may also be the least helpful for you in the event of a problem.
I believe the change from x86 numbers to proper names was also fueled by the change in Intels customers in recent years.
:)
In the 70s and 80s the majority of Intels processors were bought by computer manufacturers, rather than the public, and they were seen as the primary customer base. These people were used to dealing with electronic components by quoting only a part number, so there was no reason to give the chips real names.
Intel also knew that there were a lot of companies in silicon valley that had no products ready to produce, but wanted to stir up interest in themselves and so announced product specifications before they were available. Intel refused to give their processors funky names on the grounds that if they were not careful, people may refuse to believe they existed.
They realised in the nineties that they could make a lot of money from selling processors to the public as upgrades, and that although their processors were used in a huge percentage of the worlds computers, most people had no idea who Intel were. So they did two things. They launched the campaign called "Intel Inside", in which they gave manufacturers discounts if they put an Intel logo on the outsides of their machines, and they gave their next major product a real name, the Pentium.
Marc.