Bug 41628 - kio should implement /read/write/locking
Summary: kio should implement /read/write/locking
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2002-04-25 14:03 UTC by noselasd
Modified: 2018-10-29 02:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description noselasd 2002-04-25 13:56:49 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kio
Version:           KDE 3.0.0 
Severity:          wishlist
Installed from:    RedHat RPMs
Compiler:          gcc 2.96
OS:                Linux
OS/Compiler notes: Not Specified

Kio should have some notion of implementing lockf/flock sematicks.
as well as normal read()/write() operation.

Wold make it easier to e.g write
a network based filesystem using kio.
There is more to IO operations than
copy/move/stat and the like that kio now implements...


(Submitted via bugs.kde.org)
Comment 1 Stephan Kulow 2002-04-25 19:09:55 UTC
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Donnerstag 25. April 2002 15:56 noselasd@frisurf.no wrote:
> Package: kio
> Version: KDE 3.0.0
> Severity: wishlist
> Installed from:    RedHat RPMs
> Compiler:          gcc 2.96
> OS:                Linux
> OS/Compiler notes: Not Specified
>
> Kio should have some notion of implementing lockf/flock sematicks.
> as well as normal read()/write() operation.
>
> Wold make it easier to e.g write
> a network based filesystem using kio.
> There is more to IO operations than
> copy/move/stat and the like that kio now implements...

Hmm read and write is implemented as put/get. And flock isn't even
implemented safely in all file systems not even speaking about all
unices. How do you think we should do that?

Greetings Stephan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8yFSHwFSBhlBjoJYRAhHGAJ4sdOvI+cJkRMohUjKsCVeIP0DKgQCfZKbV
jrBq5U5wFKwBI+ih1S7Ieik=
=iplH
-----END PGP SIGNATURE-----
Comment 2 noselasd 2002-04-25 21:51:36 UTC
On Thu 2002-04-25 at 21:09 Stephan Kulow wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On Donnerstag 25. April 2002 15:56 noselasd@frisurf.no wrote:
> > Package: kio
> > Version: KDE 3.0.0
> > Severity: wishlist
> > Installed from:    RedHat RPMs
> > Compiler:          gcc 2.96
> > OS:                Linux
> > OS/Compiler notes: Not Specified
> >
> > Kio should have some notion of implementing lockf/flock sematicks.
> > as well as normal read()/write() operation.
> >
> > Wold make it easier to e.g write
> > a network based filesystem using kio.
> > There is more to IO operations than
> > copy/move/stat and the like that kio now implements...
>=20
> Hmm read and write is implemented as put/get. And flock isn't even
Seems to me that from a developers view one can only transfer a file
entierly. Appropriate for http and ftp..

What I really want is the power of gnome-vfs or what Java does with
their java.io.* and java.net.*. As well as the hooks you can provide to
the java.io.File ...

> implemented safely in all file systems not even speaking about all
> unices.=20

>How do you think we should do that?
Best effort..

--=20
Nils Olav Sel=E5sdal <NOS@Utel.no>
System Developer UtelSystems a/s
w w w . u t e l s y s t e m s . c o m
Comment 3 Nate Graham 2018-04-16 22:00:30 UTC
Is this still relevant to KDE Frameworks 5.45 or greater?
Comment 4 Andrew Crouthamel 2018-09-28 03:29:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 02:16:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!