I was stuffed in a similar way by PayPal. I purchased something from a guy on-line, paid via PayPal. The item was delivered and it was unlicensed software. I sent it back immediately. The guy wouldn't provide me with a refund. Contacted PayPal and they said that their protection agreement only covers delivery. Great - so the guy could have sent me a turd and they still wouldn't have dealt with it.
Does anyone know if this is any good at video processing? Sampling etc?
I have a need to rip frames from a Quicktime wrapped MPEG-4 source in the future, and have been looking for cross platform solutions. The client uses Mac, and the development platform is yet undecided.
Whilst it is good that we are made aware of these things, and that e-matters waited for MySQL to release a patched version, it would have been nice if they had waited for the common distributions to catch up aswell.
Yes BY do use this method, but their DHCP servers often struggle. Changes to the "Self-Care" pages can take an age to be acknowledged. If for some reason I'm not connected, re-negociating an IP address can result in MANY failures. Having said that - they "seem" to be getting better. I've had less DHCP related problems recently.
I don't think they've found the most suitable approach.
"Also, is there anything you can do to ensure that several people behind a NATing firewall all surfing to the same site don't trip the anti-DOS features?"
Whilst not totally impossible... the chances of this are SMALL. Same URI same minute... possible, same URI same second... rare I guess...
"I can easily request a couple of pages a second, if i'm spawning off links to read in the background. On the other hand wouldnt an automated attack be requesting much faster than 2 per second?"
Why would you spawn off links to the same page? Do you read the same content more than once? The key to the article is "the SAME page in the 2 second period".
Or it means that it gets it wrong 5000 times in 1 million. If it locked me out, and I retried and got in... then there is no problem with a 0.5% error.
Rather than spending time creating a PHP alternative, its a pity that some of the development effort hasn't been put into making PHP more of a stable and standard language.
I like PHP, its easy to use (given previous experience of other languages) and it allows for "fairly" rapid development. However, it really needs some fixing.
The error output is hit and miss, the function argument order is non-intuative and the documentation is lacking. The PHP API really needs freezing to allow the language to become stable and to sort some of the fundamental bugs out.
PHP is RAPIDLY becoming bloat-ware, and its a shame - cos it's nice.
Yeah - I should have explained a little more I guess. The focus of the discussion with the MS relative isn't just Web Services but also.NET. Slightly off-topic I guess.
"protocol work is starting to wind down, the infrastructure is catching up with protocols and it's time to start thinking about applications."
This quote sums up Web Services for me. The infrastructure/concept is okay... but suitable applications aren't that obvious... or maybe I've missed the point.
A relative works for MS (partly promoting Web Services) and keeps telling me that we should consider creating Web Service applications and/or converting existing applications to Web Services. My standard answer is that we can't afford to run Microsoft products on remote servers, both practically and financially. But of course the real reason is that I don't want to;). Why change what already works?
I'm not sure that it is a pointless project. The dnet project is quite interesting mainly because of the scale of the thing and the fact that they've managed to balance it all.
I would be very suprised if the future of the 'net didn't focus around sharing computational power, distributed computing and storage on-mass. As such the distributed.net effort is a great starting place to learn from.
Of course - there are still hundreds of other issues not covered by dnet. The reality of the 'net is that it is STILL in its infancy. It has a lot of growing up to do - and lot of issues still need to be solved that are currently buried deep into its complexities. Such as search engines - as the web grows these become increasing flaky.
If I find an app that does exactly want I want but has no way of outputting the result in a format I can use easily its annoying.
If I want to use an app in conjunction with another couple of apps it must fix in seemlessly. I don't want to have to download the source code to fix a strange "side effect".
Slashdot Mirror
Oh - and it was www.0800software.org.uk
"You seem to be trying to kill me - can I help?"
Does anyone know if this is any good at video processing? Sampling etc?
I have a need to rip frames from a Quicktime wrapped MPEG-4 source in the future, and have been looking for cross platform solutions. The client uses Mac, and the development platform is yet undecided.
Any other recommendations/ideas?
I really don't see how you have a case. The domain expired, they bought it. Deal with it.
Yeah *of course* ... I have a spare five minutes.
... but you knew that.
I meant package
Ahhh - okay ... another good reason to roll-your-own.
Whilst it is good that we are made aware of these things, and that e-matters waited for MySQL to release a patched version, it would have been nice if they had waited for the common distributions to catch up aswell.
After all - these bugs are pretty serious.
I started out as a member of Crosswired in the UK.
It allowed a huge amount of flexibility. Unfortunately the coop is at a point of change and so aren't accepting any members at the moment.
However, the company overseeing the project (Crosswired) will support start up coops.
It might be an interesting alternative.
Yes BY do use this method, but their DHCP servers often struggle. Changes to the "Self-Care" pages can take an age to be acknowledged. If for some reason I'm not connected, re-negociating an IP address can result in MANY failures. Having said that - they "seem" to be getting better. I've had less DHCP related problems recently.
I don't think they've found the most suitable approach.
"Also, is there anything you can do to ensure that several people behind a NATing firewall all surfing to the same site don't trip the anti-DOS features?"
... the chances of this are SMALL. Same URI same minute ... possible, same URI same second ... rare I guess ...
Whilst not totally impossible
"I can easily request a couple of pages a second, if i'm spawning off links to read in the background. On the other hand wouldnt an automated attack be requesting much faster than 2 per second?"
Why would you spawn off links to the same page? Do you read the same content more than once? The key to the article is "the SAME page in the 2 second period".
Not wanting to be pedantic ...but it is "advance" and "GHz".
;).
If you are going to criticize make sure the criticism is accurate
Or it means that it gets it wrong 5000 times in 1 million. If it locked me out, and I retried and got in ... then there is no problem with a 0.5% error.
Since when is a GUI frontend "News for Nerds. Stuff that matters"?
... urrrm ... written a front end for "grep" can I get a story posted aswell?
I have
Rather than spending time creating a PHP alternative, its a pity that some of the development effort hasn't been put into making PHP more of a stable and standard language.
I like PHP, its easy to use (given previous experience of other languages) and it allows for "fairly" rapid development. However, it really needs some fixing.
The error output is hit and miss, the function argument order is non-intuative and the documentation is lacking. The PHP API really needs freezing to allow the language to become stable and to sort some of the fundamental bugs out.
PHP is RAPIDLY becoming bloat-ware, and its a shame - cos it's nice.
Yeah - I should have explained a little more I guess. The focus of the discussion with the MS relative isn't just Web Services but also .NET. Slightly off-topic I guess.
"protocol work is starting to wind down, the infrastructure is catching up with protocols and it's time to start thinking about applications."
... but suitable applications aren't that obvious ... or maybe I've missed the point.
;). Why change what already works?
This quote sums up Web Services for me. The infrastructure/concept is okay
A relative works for MS (partly promoting Web Services) and keeps telling me that we should consider creating Web Service applications and/or converting existing applications to Web Services. My standard answer is that we can't afford to run Microsoft products on remote servers, both practically and financially. But of course the real reason is that I don't want to
Simply - Supply and Demand.
Nige.
Urrrm I didn't say I hate MS. I don't care who does it ... the whole idea is a joke.
That is the first story I've read on Slashdot that has made me feel numb. I'm scared.
I'm not sure that it is a pointless project. The dnet project is quite interesting mainly because of the scale of the thing and the fact that they've managed to balance it all.
I would be very suprised if the future of the 'net didn't focus around sharing computational power, distributed computing and storage on-mass. As such the distributed.net effort is a great starting place to learn from.
Of course - there are still hundreds of other issues not covered by dnet. The reality of the 'net is that it is STILL in its infancy. It has a lot of growing up to do - and lot of issues still need to be solved that are currently buried deep into its complexities. Such as search engines - as the web grows these become increasing flaky.
Urrrm - is a magnet next to a harddisk such a great move?
... and more information on the Digi-Q here.
There is a review of the Bit Char-G here.
It includes some better images.
Flexability is a MUST with all software.
If I find an app that does exactly want I want but has no way of outputting the result in a format I can use easily its annoying.
If I want to use an app in conjunction with another couple of apps it must fix in seemlessly. I don't want to have to download the source code to fix a strange "side effect".