I have a website hosted on a PC I have no access to. I have an upload form allowing people to upload mp3 files up to 30MB big. My server side script is done in PHP
Every time I try and upload a file, I receive an error claiming that the file exceeds the maximum size allowed, so I need to increas...
I have a web application that accepts file uploads of up to 4 MB. The server side script is PHP and web server is NGINX. Many users have requested to increase this limit drastically to allow upload of video etc.
However there seems to be no easy solution for this problem with PHP. First, on the ...
I have a web application that accepts file uploads of up to 4 MB. The server side script is PHP and web server is NGINX. Many users have requested to increase this limit drastically to allow upload of video etc.
However there seems to be no easy solution for this problem with PHP. First, on the ...
@Patrick this issue is that, while each individual request+response pair is stateless to the outside, the HTTP response itself is actually stateful. It has state: expecting headers, state: expecting body data, with order mattering.
my current thinking is that we need a combination of a higher (than 2/3) bar, and a rethink about who can vote ... but when you look at this, it looks like some pretty nice stuff wouldn't have got into php7, aswell as some stuff that was really required to fix endless sec issues with unserialize
if anything is the kind of change that requires a majority, "64 bit platform improvements for string length and integer in zval" that should, but would also fail with a higher bar ...
I don't necessarily think the votes are being influenced by people who should not be voting, but what we should do is make clear these rules so that when a contentious RFC comes along, we don't spend forever arguing about who can vote on it ...
right now there is a tendency to just announce, and keep pushing forward with your idea, in the hope that you can convince enough people to vote in the affirmative ...
that's wrong, when you experience resistance, of any kind, you should act, not argue the case, if there are changes to be made to reduce resistance, you should do it rather than spend time on internals arguing your case ...
@Patrick Can you please elaborate why exactly this is an issue for you to use Aerys at all? … Anyway, you ultimately could write your own response object with a method being passed the Aerys\Response object which you call where you'd return instead. I.e. instead of return $myResponse; you'd write $myResponse->send($AerysResponse);
@JoeWatkins There are some instances where there's nothing to act on. If I do a, the one half complains; if I do b, the other half complains
@bwoebi Because the API doesn't make sense to me. request in - response out is what I want. If I have to worry about side effects in my request handlers (which is not some one off code, it's code that will be touched often), that's a deal breaker for me
I disagree. If I return some other stuff might happen too. Caching for example. I don't care what happens inside my handler, that responsibility is moved outside. How would you implement caching with end()?
@JoeWatkins Also, we should separate technical and not purely technical votes … I.e. give core committers some more possibility to veto a RFC based on implementation. And hold a general vote on the proposed semantics.
Hello, Im a noob thats highly frustrated with tutorials showing plain sql which is nothing less than useless unless your only on phpmyadmin. Does anyone know a good pdo tutorial for a noob. Im in a position where the material "your common sense" provided is not quite clicking in my head, but all general php and sql functions i feel i have a sturdy grasp on
but wait a minute, there's a big hole in that idea ... what happens when bob has to leave us for a couple of years for real life stuff, or niki, it's going to happen ... are we then going to say they don't have the right to vote on a thing they helped create, and probably still know more about than most of the people voting at the time ?
or maybe we can reason thus: the reason a doc maintainer is allowed to vote at all is because they have special knowledge of the current state of php, precisely because they documented it ... when you become inactive you loose that special knowledge ?
I don't want to make rules that any of us are going to curse in 5 years time as short sighted or silly
also, I'd be quite annoyed if I was stopped from voting just because I was dealing with real life, even if I had no time to vote, I should have the option ...
@MadaraUchiha can you define abstraction for this application please? I took from PDO that it out quotes input into unsyntaxed strings and sends 2 types of data the actual function then the values?
In this case, it means that you have the same, similar syntax and calls, while not caring about how queries get executed or even which database is being connected to.
yeah it's true that you wouldn't have time, but should that be enough to say that if you made time, broke out of jail, or heaved yourself out of bed to vote, that we should actually say you cannot vote ...
it's silly to talk about people in jail, I know that, I'm just trying to think of what might happen, and how we might get called stupid 5 years hence for not seeing these things ...
let's have some suggestions for what we think should qualify someone as active, then we can check who meets those criteria today ?
@JoeWatkins that's the hard problem… I'd say at least a significant contribution or multiple smaller ones in the last two years … but "multiple" and "significant" are wishywashy words in that context :-/
if we leave core voters to the side, and just concentrate on what makes a doc maintainer active, is that easier for anyone ?
@PeeHaa when the leadership is bound to change every X years, I think you create instability ...
it's not easier for me .. I totally agree with the sentiment, significant or amounting to significant, but I've no clue what that means in terms of loc or commits, or if that's even a reasonable metric ...
@MadaraUchiha Im going to digest what you've provided carefully for now so your efforts are not wasted, thank you so much. One last thing should i have a better understanding of object oriented php code before working with pdo "opinion of you"?
maybe we're looking for a way to define activity, rather than contribution ... we should not exclude those people who spend long time on bugs resolving doc bugs but not actually needing to make changes, or making few changes
but then it still suffers from the same thing, someone might be very active because they wrote bad documentation and are required to keep changing it ...
yeah it's difficult to find something with a comparable model ... but maybe it wouldn't have to be programming related, it could be anything, we are just looking for a way to determine the activeness of a member of a group ... maybe from a computer game or something in that realm ...