is the folder
> where uploaded files are to be put */
>
> to handle the upload.
>
> John
>
> From: randylb <[hidden email]
> >
> Reply-To: qooxdoo Development <[hidden email]
> >
> Date: Tue, 18 Oct 2011 10:25:42 -0700 (PDT)
> To: <[hidden emai
handle the upload.
John
From: randylb
Reply-To: qooxdoo Development
Date: Tue, 18 Oct 2011 10:25:42 -0700 (PDT)
To:
Subject: Re: [qooxdoo-devel] UploadMgr connection to Backend
So it appears as though today's update has broken my solution???
On 10/18/2011 8:32 AM, John S
velopment <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=6904604&i=1>
> >
>
> Date: Tue, 18 Oct 2011 05:29:26 -0700 (PDT)
> To: <[hidden email] <http://user/SendEmail.jtp?type=node&node=6904604&i=2>
> >
>
> Subject: Re: [
ate: Tue, 18 Oct 2011 05:29:26 -0700 (PDT)
> To: <[hidden email] >
> Subject: Re: [qooxdoo-devel] UploadMgr connection to Backend
>
> Thanks John;
>
> Actually...once we figured it out, setting the qqfile parameter turned
> out to be a fairly elegant solution for my particu
ndylb
Reply-To: qooxdoo Development
Date: Tue, 18 Oct 2011 05:29:26 -0700 (PDT)
To:
Subject: Re: [qooxdoo-devel] UploadMgr connection to Backend
Thanks John;
Actually...once we figured it out, setting the qqfile parameter turned out
to be a fairly elegant solution for my particula
Thanks John;
Actually...once we figured it out, setting the qqfile parameter turned
out to be a fairly elegant solution for my particular requirements. It
allows very good control of my file naming convention.
Unless there are other problems with the php file that you think may
jump up and bite
Hi Randy
The PHP sample was badly broken and there were unnecessary requirements of
parameter names (like qqfile). This has now been fixed in the current SVN
trunk, and the application/octet-stream is no longer used - i.e., in PHP
you can just access the $_FILES[] array as with "normal" file uplo
I think I have a solution...looks like setting the parameter "qqfile" in the
addParam directive of uploader directly serves my purpose.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/UploadMgr-connection-to-Backend-tp6886082p6902004.html
Sent from the qooxdoo mailing list arch
It's not related to qooxdoo.
It's related to how the uploadmgr contrib decide when to use xhr or forms
(depending of the browser).
That's why i asked to the cool contributor if he can think about force usage
of form, so
all browsers will send multipart.
If your server is linux/unix, you can use
not quite sure i am understanding what you are saying...I am still quite new
to qooxdoo and possibly I am not understanding some of these concepts.
As I see it...everything is working as it should except that I am not seeing
what and how to connect to handler on the server. I get what is happenin
Hi Randy,
Frank's right - it sounds like your server does not handle the
"application/octet-stream" content type. In "traditional" uploads, the
file is sent as multipart/form-data and you've probably got code that
handles that already (Google if you haven't), but for
"application/octet-stream" yo
There is 2 way:
modern browser: content-type=application/octet-stream, you have to manage
that like a PUT request
other browser: classic multipart/form-data as usual
I suggest, if you didn't point that, to sniff your network or client side
(httpwatch, httpfox, chrome console ..) to see which cont
I was able to get the upload working to the Zenesis server...I also plugged
the zenesis server into the code for my application and the upload was
successful. I then changed line 79 in Application.js to point at my server
as suggested. No success there...I am still missing something in server side
Thanks John;
Kind of thought I was over complicating...tend to do that. Will give it
a try soonest.
Thanks again...Randy
On 10/13/2011 9:39 AM, John Spackman wrote:
Hi Randy
Where does the "a1a3.model" come from - did you change the namespace of
the classes? You should only need to add the c
Hi Randy
Where does the "a1a3.model" come from - did you change the namespace of
the classes? You should only need to add the contrib into your
config.json and the generator will take care of downloading it and
compiling it into your app.
As a first step, you could try getting the demo working -
I have been trying to implement the UploadMgr library and have been able to
install implement the classes but so far I have been unable to connect the
backend and accomplish a file upload. Perhaps I am failing to grasp the
obvious...nonetheless I have had no success...any help would be
appreciated.
16 matches
Mail list logo
