Fred gave an answer already, it hasn't been implemented as round as a circlePMV wrote: Programming with network-commands is a bit more as just to say ............................................................................

Fred gave an answer already, it hasn't been implemented as round as a circlePMV wrote: Programming with network-commands is a bit more as just to say ............................................................................
Where did you get that info? there is not in the 1st post here.netmaestro wrote:SoundFrequency() is indeed vanished, enhanced by a pair of new commands, GetSoundFrequency() and SetSoundFrequency().Did SoundFrequency() be vanished?
Thanks for the explanation, that's shades some light on how and why.Fred wrote:You should take a look to the bug forums, you will see we are fixing a lot of bugs. This one was not fixable, because it was badly thinked from the start. It was an easy to use command because the server itself checked every recieved packet to see if there was the magic value set by SendNetworkFile(). The problem is if one of your client send the same magic value without sending the file after that, your server will crash. That was a security hole, which couldn't be fixed, so we removed the faulty commands. Also it's easy to replace with buildin commands, so you are not left in the dust (unlike AppleAnden wrote:So that's the pure way: If it's broken dump it on the way, fixing is for lamers only?).
You are not forced to use the newest version. Just compile your 8 year old source code with the latest PB version still supporting SendNetworkFile() (= PB 5.00) and you are done. My oldest projects are more than 10 years old and some of them were never ported to PB 4 because I didn't have the time. So if a change is necessary, I implement it and compile the source code with PB 3.94. You may download older versions from the museum link in your personal account beginning with PB 2.00...Anden wrote:It was always replaceable, but 8 years ago i decided to write a wrapper around the 2 send/receive commands to make them reliable. Which includes threading and control packets.
or jaPBeShardik wrote:Those that are using PureForm from gnozal know that even PureForm was never ported to PB 4...
The history section is not always reliable though.... I was updating an old app last week that used #PB_Font_Default, but that constant no longer exists. I checked the history but nada. Had no idea what was going on, until I read that #PB_Default is what we use now. Shame the history didn't mention this little change....netmaestro wrote:PB Help -> History
Hang on a sec.... we're responsible if our client didn't follow through without sending a file..... so why should you remove it just to protect us from ourselves???? What if I want to use those commands for my own in-house app, and I know for sure the file *will* be sent after the magic value???? Please don't make this a new trend, where you censor and remove commands just to save us from ourselves. Why not trust us to code correctly??? I find this a bit insulting, actually.Fred wrote:The problem is if one of your client send the same magic value without sending the file after that, your server will crash.
It's because it is a security vulnerability. Just because you *might* use it in a closed environment doesn't mean that somebody else will read the manual and follow the advisory. Either use the alternative method to send a file or use an older PB version. And is there *REALLY* any need for the attitude?American Ninja wrote:Hang on a sec.... we're responsible if our client didn't follow through without sending a file..... so why should you remove it just to protect us from ourselves???? What if I want to use those commands for my own in-house app, and I know for sure the file *will* be sent after the magic value???? Please don't make this a new trend, where you censor and remove commands just to save us from ourselves. Why not trust us to code correctly??? I find this a bit insulting, actually.Fred wrote:The problem is if one of your client send the same magic value without sending the file after that, your server will crash.
What's next? Removing DeleteDirectory() in case we use it on C:\Windows\System32 ???
+1American Ninja wrote:I'm supposed to just shut up
I take it that means you want me to shut up??? Very well, then... I see the bigger picture of these forums now... interesting.rsts wrote:+1American Ninja wrote:I'm supposed to just shut up