Hi Petr,

So I’ve tried that - there is everything but Qt 4 :( on our servers. Only Qt 3 is present at the moment, so I can’t test it…

What about compiling Qt4 first? ;-) It would have been nice to test it but no worries if it does not work.

Btw, I’ve been thinking whether it will be a good idea to create a simple wrapper around PeerInfo (Uri). What I mean are setters and getters to keep the interface abstraction on the same level. If one wants to add host/port, there is currently no problem:

I was thinking about that one too. That will also solve our static initialization dependency problem I think. I was thinking about using a static scheme class but such a class will not be so easy to use. Maybe a high-level wrapper (what we used to have) will actually be better.

So I suggest to create an adapter over Uri with setters (and ctor) like setHost();, setPort(); and setPeerId(); and we’ll be able to get the Uri object by calling something like toUri();

Sounds nice!

Regards,

Peter