in reply to Re^6: File upload under Apache2
in thread File upload under Apache2

Yes, maybe the OP could have read a bit more documentation but sometimes this is very confusing for the beginner.

But the op wasn't even aware of CGI.pm's documentation

File upload with CGI is a bit unintuitive at first because, intuitively, you expect to do some actual upload and it takes some time to realise that you are actually just copying a file that is already in some temp folder on local disk by the time you get to use it.

That makes no sense, whats intuition got to do with it? The CGI documentation explains clearly that the uploads end up in a temp directory.

Besides, the OP did show code but wasn't yet in a position to fully understand what it does. I think it is fair to ask for some hints in that case.

Show your code is a strong hint

Replies are listed 'Best First'.
Re^8: File upload under Apache2
by tospo (Hermit) on Aug 17, 2010 at 08:06 UTC
    no flame war please. Just one thing: if intuition had nothing to do with programming then I guess we wouldn't all be spending so much time designing APIs that aim to be intuitively useful.
      Just one thing: if intuition had nothing to do with programming then I guess we wouldn't all be spending so much time designing APIs that aim to be intuitively useful.

      That is classical logical fallacy. First step to programming is reading the documentation. Reading doesn't require intuition.

        oh come on - if we are talking about code and APIs then intuitive usability is what everybody is going for. That's simply a philosphy/point of view, whatever you want to call it but certainly not "logical fallacy".

        Anyway, in this case it's not about the API of CGI.pm not being intuitive but about the fact that a file "upload" in CGI.pm is a simple read/write and not something involving any network traffic at all which is, at first, not so intuitive. Even reading the manual you might, at first, not quite understand and then ask here for clarification. I can't see anything wrong with that. Anyway, enough for one thread...