Re: PeerInfo and PeerId

Hi Peter,

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

I’ll give it a try and let you know ;).

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!

Great! So I’ll write it and we’ll see.

Have a nice day,

Petr

Would you like to post a relpy?


This post is a reply to:
Re: PeerInfo and PeerId
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 (more...)

Follow-ups:
Re: PeerInfo and PeerId
Hi Petr, Just checked you new revision with PeerInfo - the class looks quite neat :-) I was thinking that we could also provide a named ctor fromUri() to complement the toUri() (more...)