Store server data on client

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • suresh_nsnguys
    New Member
    • Aug 2006
    • 32

    Store server data on client

    Hi,

    Whether its possible to store the server data(jpg,flash and movie files) in the client hard disk.because i heard we can loaded in to RAM using javascript preloader .Its getting loaded in to RAM.but i want to store the same data in to hard disk.

    Basically if system got shut down,the data from RAM will be lost.If we store in the hard disk.the data will be there after user reboots.

    whether my concept is right, I have only little knowledge regarding javascript.can we achieve this task using javascript.plz help me this issue.I am looking forward for some help from you.

    A.suresh
  • acoder
    Recognized Expert MVP
    • Nov 2006
    • 16032

    #2
    Changed thread title.

    Comment

    • acoder
      Recognized Expert MVP
      • Nov 2006
      • 16032

      #3
      Usually the browser stores images, scripts, etc. in a temporary folder. This improves loading of the page the next time it is visited. This is not set using javascript.

      Comment

      • pbmods
        Recognized Expert Expert
        • Apr 2007
        • 5821

        #4
        Originally posted by suresh_nsnguys
        Basically if system got shut down,the data from RAM will be lost.If we store in the hard disk.the data will be there after user reboots.
        If this is the kind of behavior you're looking for, you'd probably be better off either producing a desktop application (i.e., standalone application, not run through the browser), or if it has to use web technologies, you'll probably want to either send your Users the content on a CD or prompt the User to download your files, then use a local reference in the HTML.

        The only problem with this is your file paths will depend on:
        1. Where the User puts the files, and
        2. The operating system of the User's computer.


        Now, if you package your site completely on a CD or in a folder and have the User load your site 'locally' (in other words, they would type "file:///path/to/your/file.html" instead of "http://yoursite.com/path/to/your/file.html"), then you would be able to exercise a reasonable amount of control over your content.

        For example, if you put your site on a CD, and the file structure looked something like this:

        CD
        • index.html
        • images
          • image1.jpg


        You could assert with a pretty high level of confidence that if you used this line in index.html:

        [HTML]
        <img src="images/image1.jpg" alt="A teapot for sale" />
        [/HTML]

        image1.jpg would show up in your User's browser when he loaded index.html from the CD.

        Comment

        Working...