WebObjects is server technology not a client side application technology. For networking on the iPhone and OS X you can use BSD sockets or there are some objective-c wrappers around them if you don't want to do the raw C code yourself.
The iPhone 1.0 was not ready for 3rd party development. If you have been following the SDK releases you can see that they have been changing at a very rapid pace. The early iPhone software was basically not ready for people to use and the API was not stable. Giving people the ability to develop web apps that looked like native apps was the best thing they could do at the time.
Now that they are stabilizing the APIs, people can write native applications. The iPhone at the beginning was already lagging a bit IMO and you can see that because they had to delay Leopard to work on it.
Once you get around the syntax, Objective-C is not hard to use at all. The language runtime is very dynamic and memory management is easy reference counting or garbage collected if you want(but no GC on iPhone). I came from the standard C/C++ background and I found it a little weird after using C/C++ for many years but you can pick up Objective-C relatively fast. The big learning curve is learning what frameworks and APIs you need to use to do what you want which requires lots of learning and/or looking up things all the time but that's really the same with any other frameworks.
EDGE is not very fast and for VOIP you need some low latency which EDGE doesn't seem to provide most of the time. When they go to 3G then we'll see what happens.
I have no idea. Bell is actually hiding a lot of information from the public. They had to reply to the CRTC but all their numbers are not available to the public or the CAIP.
The 3rd party firmware products like dd-wrt and tomato only does upstream QoS by default. You can make your own iptables script for the down stream though. I'm not sure how it works in implementation but I've set mine to give http full bandwidth over nntp on a certain port.
When I'm not using http to download something then nntp can download at full speed. When I do something on http it will get the full bandwidth. It's not instant though so it takes a few seconds to kick in. I suspect it's dropping ACKs for the nntp traffic or something like that so that the nntp server stops sending so much data.
You could do the same thing with bittorrent as long as you know the ports.
That sounds pretty interesting. I wonder how deep the DPI actually is. If you just send a body tag and head tag and put some binary in between, I wonder if it'll detect it as http or what.
They should be able to do what they want on Sympatico, but that is supposed to be separate from Bell Canada. Bell Canada has to give access to 3rd party companies. That means the 3rd party company pays Bell for dedicated links over their ATM network. The 3rd party provides their own connection to the internet backbone. Bell is only providing ATM transit. That is the problem. Bell Nexxia is supposed to be separated from Sympatico. One is an internet service(Sympatico), the other is the core network.
They are screwing with data for other companies. Imagine that Peer 1 started throttling torrents over their network because they say it takes up too much bandwidth. People would be outraged.
I do this at home, but on a port basis. Basically I have DD-WRT and an iptables script which allows NNTP traffic on a certain port to be throttled when there's http traffic. If I download a big file say some movie trailer from Apple.com, the usenet traffic goes to almost zero. I think I let it have 10kbps minimum. They have these fancy DPI boxes and they could easily tag torrent packets to low priority and configure their routers to obey QOS tags. If the link really gets congested the the whole thing will work itself out because http(s), pop, imap etc. are all easy to detect. Give those higher priority and whenever a non bulk packet comes along it will get out before the rest.
That's funny because my AppleTV is silent. Certainly there's no fan noise so I don't buy that explaination. When you're watching TV or something off of the device you can't hear it because of the TV sound. Even when everything is off it's silent unless you put your head up to it and then you can hear the hard drive a little bit.
Their ATM capacity is around 170 Gbit/s and their backbone traffic is around 125Gbit/s. They have 45Gbit of spare capacity and this is Bell's own numbers so who knows if they're inflated or not. Also, their DSLAM capacity is enormous so where exactly is the congestion? Maybe there are some DSLAMs that are congested but that's why you upgrade, not throttle your entire network and all 3rd party traffic over the ATM network.
He argues that if there is not full disclosure and you just notify the vendors that the bad guys will "probably" know about it too. If that was wide spread then you wouldn't have people reverse engineering the monthly Windows patches to figure out what was patched. There are many crackers doing this every time Microsoft comes out with new updates and then they use that information to exploit people who haven't patched.
If the exploits were fully disclosed instead then most likely there would be even more exploits in the wild.
If you can do that with iptables then you could do it with a home router and a 3rd party firmware on it. DD-WRT has iptables and I believe Tomato does as well.
When you go to the USA you have to go through US Customs and I doubt they'd respect any Canadian Charter of Rights and Freedoms acts. That's the big problem IMO. But also, I don't see how they can reasonably test for this anyways without holding up all the people at the border.
I don't know but it says evaporative cooling which is just the typical cooling you see on commercial buildings. Those big square things on the roofs are the cooling towers.
They claim to be cutting edge & everything yet they are using the same old evaporative cooling that every other commercial building uses. How about using something more sustainable in the long run like geothermal. Commercial geothermal may be more expensive up front but dumping the heat in the ground will save so much money and water in the long run. 3 MILLION gallons a day is retarded. Talk about wasteful, especially in a desert area.
Yeah, yeah, we all know that. Just because there's lots of legitimate uses doesn't mean 90% of bittorrent usage is for downloading tv shows and other things. Right now I'm downloading a Cocoa Heads meeting video and throttled to insanely slow speeds that make it take 3 days to get 1.2 GB worth of video. That's completely a legitimate thing I'm using it for but you still can't pretend that most of the use at the moment is non legitimate or illegally distributed copyrighted material.
Tomato actually applies settings without dropping your pppoe session. Every time I make any little change even to the wireless network, dd-wrt drops my IP and I have to wait for it to re-log in and get an IP. In this day that shouldn't happen.
Slashdot Mirror
WebObjects is server technology not a client side application technology. For networking on the iPhone and OS X you can use BSD sockets or there are some objective-c wrappers around them if you don't want to do the raw C code yourself.
The iPhone 1.0 was not ready for 3rd party development. If you have been following the SDK releases you can see that they have been changing at a very rapid pace. The early iPhone software was basically not ready for people to use and the API was not stable. Giving people the ability to develop web apps that looked like native apps was the best thing they could do at the time.
Now that they are stabilizing the APIs, people can write native applications. The iPhone at the beginning was already lagging a bit IMO and you can see that because they had to delay Leopard to work on it.
Once you get around the syntax, Objective-C is not hard to use at all. The language runtime is very dynamic and memory management is easy reference counting or garbage collected if you want(but no GC on iPhone). I came from the standard C/C++ background and I found it a little weird after using C/C++ for many years but you can pick up Objective-C relatively fast. The big learning curve is learning what frameworks and APIs you need to use to do what you want which requires lots of learning and/or looking up things all the time but that's really the same with any other frameworks.
EDGE is not very fast and for VOIP you need some low latency which EDGE doesn't seem to provide most of the time. When they go to 3G then we'll see what happens.
I have no idea. Bell is actually hiding a lot of information from the public. They had to reply to the CRTC but all their numbers are not available to the public or the CAIP.
The 3rd party firmware products like dd-wrt and tomato only does upstream QoS by default. You can make your own iptables script for the down stream though. I'm not sure how it works in implementation but I've set mine to give http full bandwidth over nntp on a certain port.
When I'm not using http to download something then nntp can download at full speed. When I do something on http it will get the full bandwidth. It's not instant though so it takes a few seconds to kick in. I suspect it's dropping ACKs for the nntp traffic or something like that so that the nntp server stops sending so much data.
You could do the same thing with bittorrent as long as you know the ports.
That sounds pretty interesting. I wonder how deep the DPI actually is. If you just send a body tag and head tag and put some binary in between, I wonder if it'll detect it as http or what.
They should be able to do what they want on Sympatico, but that is supposed to be separate from Bell Canada. Bell Canada has to give access to 3rd party companies. That means the 3rd party company pays Bell for dedicated links over their ATM network. The 3rd party provides their own connection to the internet backbone. Bell is only providing ATM transit. That is the problem. Bell Nexxia is supposed to be separated from Sympatico. One is an internet service(Sympatico), the other is the core network.
They are screwing with data for other companies. Imagine that Peer 1 started throttling torrents over their network because they say it takes up too much bandwidth. People would be outraged.
I do this at home, but on a port basis. Basically I have DD-WRT and an iptables script which allows NNTP traffic on a certain port to be throttled when there's http traffic. If I download a big file say some movie trailer from Apple.com, the usenet traffic goes to almost zero. I think I let it have 10kbps minimum. They have these fancy DPI boxes and they could easily tag torrent packets to low priority and configure their routers to obey QOS tags. If the link really gets congested the the whole thing will work itself out because http(s), pop, imap etc. are all easy to detect. Give those higher priority and whenever a non bulk packet comes along it will get out before the rest.
How is that? It's Microsoft's DRM. If they really wanted it available on OS X they could port it over.
In 20 years in the USA when the internet on this continent can handle it or in Japan today you can have streaming 720p.
That's funny because my AppleTV is silent. Certainly there's no fan noise so I don't buy that explaination. When you're watching TV or something off of the device you can't hear it because of the TV sound. Even when everything is off it's silent unless you put your head up to it and then you can hear the hard drive a little bit.
Look at the Bell provided graphs:
http://www.dslreports.com/forum/r20567537-
Their ATM capacity is around 170 Gbit/s and their backbone traffic is around 125Gbit/s. They have 45Gbit of spare capacity and this is Bell's own numbers so who knows if they're inflated or not. Also, their DSLAM capacity is enormous so where exactly is the congestion? Maybe there are some DSLAMs that are congested but that's why you upgrade, not throttle your entire network and all 3rd party traffic over the ATM network.
He argues that if there is not full disclosure and you just notify the vendors that the bad guys will "probably" know about it too. If that was wide spread then you wouldn't have people reverse engineering the monthly Windows patches to figure out what was patched. There are many crackers doing this every time Microsoft comes out with new updates and then they use that information to exploit people who haven't patched.
If the exploits were fully disclosed instead then most likely there would be even more exploits in the wild.
True, but if you really care about trying to get around it then you can spend the $50-60 to buy one if it doesn't.
If you can do that with iptables then you could do it with a home router and a 3rd party firmware on it. DD-WRT has iptables and I believe Tomato does as well.
When you go to the USA you have to go through US Customs and I doubt they'd respect any Canadian Charter of Rights and Freedoms acts. That's the big problem IMO. But also, I don't see how they can reasonably test for this anyways without holding up all the people at the border.
Yeah, I'm sure all those engineers planning for 10 years don't know what they're doing.
With space missions it's much better if you can get your fuel outside of Earth because of the weight issue.
I don't know but it says evaporative cooling which is just the typical cooling you see on commercial buildings. Those big square things on the roofs are the cooling towers.
No you can't do that though because the water evaporates into the air. Doing that removes heat from the circulating fluid in the heat exchanger.
They claim to be cutting edge & everything yet they are using the same old evaporative cooling that every other commercial building uses. How about using something more sustainable in the long run like geothermal. Commercial geothermal may be more expensive up front but dumping the heat in the ground will save so much money and water in the long run. 3 MILLION gallons a day is retarded. Talk about wasteful, especially in a desert area.
Yeah, yeah, we all know that. Just because there's lots of legitimate uses doesn't mean 90% of bittorrent usage is for downloading tv shows and other things. Right now I'm downloading a Cocoa Heads meeting video and throttled to insanely slow speeds that make it take 3 days to get 1.2 GB worth of video. That's completely a legitimate thing I'm using it for but you still can't pretend that most of the use at the moment is non legitimate or illegally distributed copyrighted material.
Works on Leopard :)
Tomato actually applies settings without dropping your pppoe session. Every time I make any little change even to the wireless network, dd-wrt drops my IP and I have to wait for it to re-log in and get an IP. In this day that shouldn't happen.