This is a multi-part message in MIME format.
------=_NextPart_000_00F0_01C11F3D.BD88CD90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am creating a I/O Slave (for now "hello" is the protocol name
I am using).
I have found that if I create a TransferJob by calling the following:
transferJob =3D KIO::get( "hello:foo" );
vs
transferJob =3D KIO::get( "hello://foo" );
the 'mimetype' method of the I/O slave gets invoked for
the first call -- get("hello:foo") -- but not the second.
The second call uses the defaultMimetype value specified in
the hello.protocol file in the /usr/share/services directory.
Any clue why this is?
Ben Schepens
schepens@mindspring.com
------=_NextPart_000_00F0_01C11F3D.BD88CD90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am creating a I/O Slave (for now =
"hello" is the=20
protocol name
I am using).
I have found that if I create a =
TransferJob=20
by calling the following:
transferJob =3D KIO::get( =
"hello:foo"=20
);
vs
transferJob =3D KIO::get( "hello://foo" );
the =
'mimetype' method of the I/O slave gets invoked for
the first call -- =
get("hello:foo") -- but not the second.
The second call uses the=20
defaultMimetype value specified in
the hello.protocol file in the=20
/usr/share/services directory.
Any clue why this is?
Ben=20
Schepens
schepens@mindspring.com
------=_NextPart_000_00F0_01C11F3D.BD88CD90--
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<