[ale] OT: content-disposition and client-side perl

James P. Kinney III jkinney at localnetsolutions.com
Thu Jun 13 18:03:07 EDT 2002


Jenn,

This will accept a string piped to it as below:

#!/usr/bin/perl

$in=<STDIN>;

print "the input was $in\n";

call it with:

 echo "test string2" | ./test.pl

On Thu, 2002-06-13 at 11:20, jenn at colormaria.com wrote:
> The idea is to sort of make the perl app work like adobe acrobat, where
> the server pushes a stream of text for the app to interpret without
> saving the stream to a physical file and then reading it in.  My only
> frame of reference would be piping stdin to a script, so I'm really in
> over my head here.
> 
> I've considered making the client-side perl app pull the file instead
> of having the server push the file to the app, but the file is hidden
> behind many layers of authentication and ssl and frankly, I'd rather
> tackle trying to read pushed data than sort out logging in, hitting a
> script with a request to fetch the file from its non-web-accessible
> location, etc.
> 
> Thanks for the feedback...you've given me some ideas on new stuff to
> search for on Google.  :)
> 
> jenn
> 
> > It sounds like the perl app doesn't accept/understand the sequencing
> > from the web call. Maybe the perl app need to be simply passed a URL
> to
> > get the data file instead of being shoved it. I'm not sure how to pass
> > a data file to an external app. Passing a string should be easy
> enough.
> > This also would allow the appearance of faster start-up time. The app
> > can start building the on-screen window while the download thread
> grabs
> > the data file.
> >
> > On Thu, 2002-06-13 at 01:20, jenn at colormaria.com wrote:
> >> I'm trying to do the following, and I don't even know where to start
> >> looking forassistance:
> >>
> >> 0 - User registers application in browser to handle .cex (custom
> >> extension, as an example only) with a client side perl script I've
> >> written. 1 - User hits web application, which generates text for them
> >> to d/l. 2 - Web app sends these headers:
> >>       content-type = application/cex;
> >>       content-disposition = inline; filename=myfile.cex;
> >>       content-length = 1024;
> >>
> >> 3) perl script on client side reads in data and does its thing (using
> >> perl/TK,this is a windows app, blech).
> >>
> >> So I've got 0-2 working great.  And if I *download* the file, I can
> >> run the perlscript just fine.  The missing piece is, how on earth can
> >> I make perl read thedata being pushed by the browser as if it were
> >> STDIN ??
> >>
> >> If anyone has any resources for something like this, search phrases
> to
> >> hit google/devshed with, anything at all I would be eternally
> >> grateful.   In theoryit should be doable but I am boggled as to how.
> >>
> >> TIA!
> >> jenn
> >>
> >>
> >>
> >>
> >> ---
> >> This message has been sent through the ALE general discussion list.
> >> See http://www.ale.org/mailing-lists.shtml for more info. Problems
> >> should be  sent to listmaster at ale dot org.
> > --
> > James P. Kinney III   \Changing the mobile computing world/
> > President and CEO      \          one Linux user         /
> > Local Net Solutions,LLC \           at a time.          /
> > 770-493-8244             \.___________________________./
> >
> > GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
> > <jkinney at localnetsolutions.com>
> > Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
> 
> 
> 
> 
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
> sent to listmaster at ale dot org.
-- 
James P. Kinney III   \Changing the mobile computing world/
President and CEO      \          one Linux user         /
Local Net Solutions,LLC \           at a time.          /
770-493-8244             \.___________________________./

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7 




---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.






More information about the Ale mailing list