[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: QNetworkAccessManager and KDE's KIO
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2012-03-22 22:53:30
Message-ID: 1691884.JYcUg6Ua3d () xps
[Download RAW message or body]

El Dimarts, 20 de mar=E7 de 2012, a les 12:26:05, Weng Xuetian va escriure:
> Hi,

Hi

> I'm currently implementing a library that require network access, and I n=
eed
> some custom url such as "myapp://" to do oauth callback, so I create a
> class inherits QNetworkAccessManager.
> =

> But I found if anyone want to KDE's KIO::Integration::AccessManager to
> replace the NetworkAccessManager in order to use KDE proxy setting and KI=
O,
> there will be some problem. I don't want this library hardly depends on
> KDE, but I also hope it can integrate with KDE well.
> =

> I read attica's code but seems it use a custom interface, which is not
> fesible here since I need to set the NetworkAccessManager to the QWebView.
> =

> Any idea about how to solve this problem? Is simply keep a pointer to the
> old networkmanager and redirect createRequest to it enough?

I think you could make your QNetworkAccessManager have a =

setNonMyAppAccessManager() and then all the calls that happen to your =

MyAppNetworkAccessManager that are not myapp:// you redirected them to the =

QNetworkAccessManager passed there.

I'm not a huge expert in QNetworkAccessManager but it could work. So give i=
t a =

try :-)

Cheers,
  Albert

> =

> Thanks!

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscrib=
e <<
[prev in list] [next in list] [prev in thread] [next in thread]