Bart said:
Only if your .ini file resides on the same domain, you can read it by
javascript in modern browsers. A popular technique is the use of
iframes:
<iframe src="C:\YOUR_INI_FILE.INI"></iframe>
<OT>
JFTR:
If you consider `localhost' a domain and you dare call IE a "modern
browser" this might work. Generally, not backslashes serve the purpose
of path delimiters in URIs but forward slashes do. And a URI scheme
identifier is missing, too, Mozilla/5.0 for example will probably not
show anything (at least it will only work on Windows.)
<iframe src="file:///C:/YOUR_INI_FILE.INI"></iframe>
could work on Windows as well as
<iframe src="YOUR_INI_FILE.INI"></iframe>
could do everywhere. However, the former will only work if the
parent document is accessed via the local file system or if the UA
is borken/unpatched. AFAIK & IIRC, for Mozilla/5.0 the bug has
been fixed in rv:1.4 (CMIIW), and thus access from `http:' to
`file:' is no longer possible.
Saving back is not possible. You 'll need a server process for that.
Just to clarify: Server processes cannot and will not access the
`iframe' element (since it is rendered client-side), but the
resource it refers to.
</OT>
PointedEars