You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Heligon Sandra <sa...@nextream.fr> on 2002/12/09 10:16:51 UTC
Access/Manage client's file system
Sorry not to have answered earlier but I did not work Friday.
By 'local' I mean the client's machine not the server.
First, the server offers templates to the client.
Example of JSP:
Name = Toto; Type = Data; Value = 12; etc....
<<Save>> <<Load>> <<Apply>> <<Cancel>>
If the user select the save button I would like to save data on the
client's machine and the load button allows to load a file from the
client's machine.
We could store instances of the template on the server but it is
specific
to each client that's why we think that it is better to allow the
client to
access file system. For us server allows to store only common data.
If you think it is better to save data on the server, thanks to
explain.
Do you understand my question better ?
If I understand your reply, to do that I must use Client plugin
technologies.
Do you have an example ?
Thanks a lot
Sandra
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Access/Manage client's file system
Posted by micael <ca...@harbornet.com>.
But Andrew, this would involve the client putting information on the
server, then downloading it to the client. That is just a tad inefficient,
wouldn't you say?
At 06:36 PM 12/9/2002 +0800, you wrote:
>Well, if you can make do with something thats rather user unfriendly you can
>use the standard html stuff:
>For the files to be saved on the users machine you could provide a link -
>clicking the link will allow the user to download the file which they can
>save on their machine.
>For the server to read the file you provide a file upload field and the user
>browses through their filesystem for the file required. Of course its a very
>manual process which is a lot more messy than the interface you hope for in
>your example and in both cases you have no control over the file names used.
>It is up to the user to choose where to save it, and also up to the user to
>select which file to send back.
>
>-----Original Message-----
>From: Heligon Sandra [mailto:sandra.heligon@nextream.fr]
>Sent: Monday, December 09, 2002 17:17
>To: 'struts-user@jakarta.apache.org'
>Cc: 'caraunltd@harbornet.com'; 'marklowe@libero.it'
>Subject: Access/Manage client's file system
>
>
>
> Sorry not to have answered earlier but I did not work Friday.
> By 'local' I mean the client's machine not the server.
> First, the server offers templates to the client.
> Example of JSP:
> Name = Toto; Type = Data; Value = 12; etc....
> <<Save>> <<Load>> <<Apply>> <<Cancel>>
> If the user select the save button I would like to save data on the
> client's machine and the load button allows to load a file from the
>client's machine.
> We could store instances of the template on the server but it is
>specific
> to each client that's why we think that it is better to allow the
>client to
> access file system. For us server allows to store only common data.
> If you think it is better to save data on the server, thanks to
>explain.
> Do you understand my question better ?
> If I understand your reply, to do that I must use Client plugin
>technologies.
> Do you have an example ?
> Thanks a lot
> Sandra
>
>
>
>
>
>--
>To unsubscribe, e-mail:
><ma...@jakarta.apache.org>
>For additional commands, e-mail:
><ma...@jakarta.apache.org>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
Micael
-------------------------------------------------------
This electronic mail transmission and any accompanying documents contain
information belonging to the sender which may be confidential and legally
privileged. This information is intended only for the use of the
individual or entity to whom this electronic mail transmission was sent as
indicated above. If you are not the intended recipient, any disclosure,
copying, distribution, or action taken in reliance on the contents of the
information contained in this transmission is strictly prohibited. If you
have received this transmission in error, please delete the message. Thank
you
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Access/Manage client's file system
Posted by Frederico Schuh <fr...@yahoo.com.br>.
I don't think storing this on the client is a good
approach to doing it... if you choose to do this, then
you're breaking one of the Web's main advantages,
which is client independency (you will most likely
lock the user to a single browser that supports a
specific plugin, 95% chance that it will be IE).
You should really consider using the server to handle
the templates. Do you have many clients accessing this
application? Are the templates too big, and do you
have many of these files for each user? You could even
consider using a database to store templates, and read
them when the user needs their data. Then you could
save them in the user's session for optimal
performance. There are many ways of doing it, but it
all depends on how you are going to use the files.
--- Heligon Sandra <sa...@nextream.fr> wrote:
>
> Sorry not to have answered earlier but I did not
> work Friday.
> By 'local' I mean the client's machine not the
> server.
> First, the server offers templates to the client.
> Example of JSP:
> Name = Toto; Type = Data; Value = 12; etc....
> <<Save>> <<Load>> <<Apply>> <<Cancel>>
> If the user select the save button I would like to
> save data on the
> client's machine and the load button allows to load
> a file from the
> client's machine.
> We could store instances of the template on the
> server but it is
> specific
> to each client that's why we think that it is
> better to allow the
> client to
> access file system. For us server allows to store
> only common data.
> If you think it is better to save data on the
> server, thanks to
> explain.
> Do you understand my question better ?
> If I understand your reply, to do that I must use
> Client plugin
> technologies.
> Do you have an example ?
> Thanks a lot
> Sandra
>
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
=====
----------------------------------------
Frederico Ferro Schuh
fred_schuh@yahoo.com.br
ICQ: 20486081
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Access/Manage client's file system
Posted by Mark <ma...@libero.it>.
Micael who responded to this message says he's working on something similar.
To be honest I don't know any nice, cross browser way of doing this.
I'd have thought the money you save on disk space would swallowed up by
extra development time.
However if I had to do this i'd be reading stuff about soap and/or similar
stuff.
The filesystem couild be controled by and application that you distribute to
recienve soap envelopes and run various file system operations. I believe
flash is capable of this (i'd be interested to know).
Server sends soap envelope to flash movie > flash unwraps envelope and runs
commands based on contents.
The big quest for me remains can you do file system stuff from a flash
movie? My concern would be how many work arounds you'd have to do for flash
because those crazy macromedia kids may have been on the crack again. A java
applet could also be used, but i believe these days more people have flash
than java plugins.
Also do the directories remain on the local machine after the operations? Or
are they created and removed each time the user wants to do his/her stuff? T
Things i'd do in your shoes.. Make or find a flash movie that reads and
writes soap, make or find a flash movie that performs file system
operations. Get my hands on the jakarta soap tags that should help you work
out what you want you java classes to do.
Cheers mark
On 9-12-2002 10:16, "Heligon Sandra" <sa...@nextream.fr> wrote:
>
> Sorry not to have answered earlier but I did not work Friday.
> By 'local' I mean the client's machine not the server.
> First, the server offers templates to the client.
> Example of JSP:
> Name = Toto; Type = Data; Value = 12; etc....
> <<Save>> <<Load>> <<Apply>> <<Cancel>>
> If the user select the save button I would like to save data on the
> client's machine and the load button allows to load a file from the
> client's machine.
> We could store instances of the template on the server but it is
> specific
> to each client that's why we think that it is better to allow the
> client to
> access file system. For us server allows to store only common data.
> If you think it is better to save data on the server, thanks to
> explain.
> Do you understand my question better ?
> If I understand your reply, to do that I must use Client plugin
> technologies.
> Do you have an example ?
> Thanks a lot
> Sandra
>
>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Access/Manage client's file system
Posted by micael <ca...@harbornet.com>.
If nothing else, you could have a web app that zips up the files and sends
them as one. The other thing is that you could have a refresh on the
response (request) that will activate when a file download finishes,
starting the next one until you are done. But, zip is best, I think. Why
use the web for this?
Micael
At 06:05 PM 12/9/2002 +0530, you wrote:
>a little off the topic..
>
>but is it possible to download multiple files using a single response from
>the server.
>Something like multiple upload to the server .. just that this case .. i
>want the client (browser/client application) to DOWNLOAD multiple file in a
>SINGLE response from the server..
>
>am i clear.. enough??
>
>subhro.
>
>----- Original Message -----
>From: "Andrew Hill" <an...@gridnode.com>
>To: "Struts Users Mailing List" <st...@jakarta.apache.org>
>Sent: Monday, December 09, 2002 4:06 PM
>Subject: RE: Access/Manage client's file system
>
>
> > Well, if you can make do with something thats rather user unfriendly you
>can
> > use the standard html stuff:
> > For the files to be saved on the users machine you could provide a link -
> > clicking the link will allow the user to download the file which they can
> > save on their machine.
> > For the server to read the file you provide a file upload field and the
>user
> > browses through their filesystem for the file required. Of course its a
>very
> > manual process which is a lot more messy than the interface you hope for
>in
> > your example and in both cases you have no control over the file names
>used.
> > It is up to the user to choose where to save it, and also up to the user
>to
> > select which file to send back.
> >
> > -----Original Message-----
> > From: Heligon Sandra [mailto:sandra.heligon@nextream.fr]
> > Sent: Monday, December 09, 2002 17:17
> > To: 'struts-user@jakarta.apache.org'
> > Cc: 'caraunltd@harbornet.com'; 'marklowe@libero.it'
> > Subject: Access/Manage client's file system
> >
> >
> >
> > Sorry not to have answered earlier but I did not work Friday.
> > By 'local' I mean the client's machine not the server.
> > First, the server offers templates to the client.
> > Example of JSP:
> > Name = Toto; Type = Data; Value = 12; etc....
> > <<Save>> <<Load>> <<Apply>> <<Cancel>>
> > If the user select the save button I would like to save data on the
> > client's machine and the load button allows to load a file from the
> > client's machine.
> > We could store instances of the template on the server but it is
> > specific
> > to each client that's why we think that it is better to allow the
> > client to
> > access file system. For us server allows to store only common data.
> > If you think it is better to save data on the server, thanks to
> > explain.
> > Do you understand my question better ?
> > If I understand your reply, to do that I must use Client plugin
> > technologies.
> > Do you have an example ?
> > Thanks a lot
> > Sandra
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >
> >
> > --
> > To unsubscribe, e-mail:
><ma...@jakarta.apache.org>
> > For additional commands, e-mail:
><ma...@jakarta.apache.org>
> >
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
Micael
-------------------------------------------------------
This electronic mail transmission and any accompanying documents contain
information belonging to the sender which may be confidential and legally
privileged. This information is intended only for the use of the
individual or entity to whom this electronic mail transmission was sent as
indicated above. If you are not the intended recipient, any disclosure,
copying, distribution, or action taken in reliance on the contents of the
information contained in this transmission is strictly prohibited. If you
have received this transmission in error, please delete the message. Thank
you
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Access/Manage client's file system
Posted by Subhrajyoti Moitra <su...@contata.co.in>.
a little off the topic..
but is it possible to download multiple files using a single response from
the server.
Something like multiple upload to the server .. just that this case .. i
want the client (browser/client application) to DOWNLOAD multiple file in a
SINGLE response from the server..
am i clear.. enough??
subhro.
----- Original Message -----
From: "Andrew Hill" <an...@gridnode.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Monday, December 09, 2002 4:06 PM
Subject: RE: Access/Manage client's file system
> Well, if you can make do with something thats rather user unfriendly you
can
> use the standard html stuff:
> For the files to be saved on the users machine you could provide a link -
> clicking the link will allow the user to download the file which they can
> save on their machine.
> For the server to read the file you provide a file upload field and the
user
> browses through their filesystem for the file required. Of course its a
very
> manual process which is a lot more messy than the interface you hope for
in
> your example and in both cases you have no control over the file names
used.
> It is up to the user to choose where to save it, and also up to the user
to
> select which file to send back.
>
> -----Original Message-----
> From: Heligon Sandra [mailto:sandra.heligon@nextream.fr]
> Sent: Monday, December 09, 2002 17:17
> To: 'struts-user@jakarta.apache.org'
> Cc: 'caraunltd@harbornet.com'; 'marklowe@libero.it'
> Subject: Access/Manage client's file system
>
>
>
> Sorry not to have answered earlier but I did not work Friday.
> By 'local' I mean the client's machine not the server.
> First, the server offers templates to the client.
> Example of JSP:
> Name = Toto; Type = Data; Value = 12; etc....
> <<Save>> <<Load>> <<Apply>> <<Cancel>>
> If the user select the save button I would like to save data on the
> client's machine and the load button allows to load a file from the
> client's machine.
> We could store instances of the template on the server but it is
> specific
> to each client that's why we think that it is better to allow the
> client to
> access file system. For us server allows to store only common data.
> If you think it is better to save data on the server, thanks to
> explain.
> Do you understand my question better ?
> If I understand your reply, to do that I must use Client plugin
> technologies.
> Do you have an example ?
> Thanks a lot
> Sandra
>
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Access/Manage client's file system
Posted by Andrew Hill <an...@gridnode.com>.
Well, if you can make do with something thats rather user unfriendly you can
use the standard html stuff:
For the files to be saved on the users machine you could provide a link -
clicking the link will allow the user to download the file which they can
save on their machine.
For the server to read the file you provide a file upload field and the user
browses through their filesystem for the file required. Of course its a very
manual process which is a lot more messy than the interface you hope for in
your example and in both cases you have no control over the file names used.
It is up to the user to choose where to save it, and also up to the user to
select which file to send back.
-----Original Message-----
From: Heligon Sandra [mailto:sandra.heligon@nextream.fr]
Sent: Monday, December 09, 2002 17:17
To: 'struts-user@jakarta.apache.org'
Cc: 'caraunltd@harbornet.com'; 'marklowe@libero.it'
Subject: Access/Manage client's file system
Sorry not to have answered earlier but I did not work Friday.
By 'local' I mean the client's machine not the server.
First, the server offers templates to the client.
Example of JSP:
Name = Toto; Type = Data; Value = 12; etc....
<<Save>> <<Load>> <<Apply>> <<Cancel>>
If the user select the save button I would like to save data on the
client's machine and the load button allows to load a file from the
client's machine.
We could store instances of the template on the server but it is
specific
to each client that's why we think that it is better to allow the
client to
access file system. For us server allows to store only common data.
If you think it is better to save data on the server, thanks to
explain.
Do you understand my question better ?
If I understand your reply, to do that I must use Client plugin
technologies.
Do you have an example ?
Thanks a lot
Sandra
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>