Found the guy and got the work done, this offer is now closed.
Topic: FOUND: C++/Qt developer for websocket server project (50~1000BTC) (Read 4914 times)
April 12, 2011, 07:32:01 PM
this guy wrote a simple websocket server in c# http://www.codeproject.com/KB/webservices/c_sharp_web_socket_server.aspx
might be a very good starting point to port it to c++/qt...
might be a very good starting point to port it to c++/qt...
April 12, 2011, 06:36:14 PM
Could you point to some documentation of this Websocket handshake you want to be implemented, because I still not sure what exactly you want to be done?
http://en.wikipedia.org/wiki/WebSockets
Support "most browsers". This means support of both:
April 12, 2011, 06:30:48 PM
Could you point to some documentation of this Websocket handshake you want to be implemented, because I still not sure what exactly you want to be done?
April 12, 2011, 06:05:26 PM
Why not just use WebKit?
It's not a websocket server but client. I need the server part.
Why does the server have to be written in C++/Qt?
Because I want to code the server part myself, there are some abstractions I want to make, and there are many other things I'd like to use this (it'd be useful for a *lot* of things)
April 12, 2011, 04:43:23 PM
Why does the server have to be written in C++/Qt?
April 12, 2011, 03:45:17 PM
Why not just use WebKit?
April 12, 2011, 09:26:42 AM
Um, I'm not sure what more do you want apart from what QtTcpServer class does? Do you want a HTTP server?
As I said, I need a websocket server. That means using QTcpServer, implementing the base of a HTTP server, and adding support for the websocket fuckedup handshake. I was hoping someone would have that already done somewhere. I may end up doing it myself if nobody takes this up.
April 12, 2011, 08:03:09 AM
* kiba stratches head.
Well, I can do node.js programming, but I don't know anything about C++/Qt. I can learn but then I don't know anything about programming the websocket protocol.
April 12, 2011, 07:46:55 AM
Um, I'm not sure what more do you want apart from what QtTcpServer class does? Do you want a HTTP server?
April 12, 2011, 05:22:27 AM
I know nothing about programming with Qt but I'm willing to learn if nobody else takes you up on this. Good luck!
April 12, 2011, 05:16:32 AM
I'd need someone to write (or find if it already exists, I'm too lazy to filter Qt results from QuickTime results in Google) a little something for me.
Basically, it'd be an async websocket server in Qt. It should not depend on QtGui (only use QCoreApplication/etc), and allow me to write my own websocket handler.
I'd bid between 50 BTC (for a link to something already existing, opensource, and which works fine) to 1000 BTC (if you make it yourself and produce a quality library, opensource or not - if opensource it shouldn't be under GPL, use a real license like BSD, X11 or WTFPL). In between amounts for in between results. First come first served, etc.
Some additionnal details:
Let me know if you need additional details.
Basically, it'd be an async websocket server in Qt. It should not depend on QtGui (only use QCoreApplication/etc), and allow me to write my own websocket handler.
I'd bid between 50 BTC (for a link to something already existing, opensource, and which works fine) to 1000 BTC (if you make it yourself and produce a quality library, opensource or not - if opensource it shouldn't be under GPL, use a real license like BSD, X11 or WTFPL). In between amounts for in between results. First come first served, etc.
Some additionnal details:
- Each connected socket should be represented by an abstract object, with slots for incoming data, and the ability to send data to the endpoint
- No form of serialization is required, I'll handle that myself
- It should use QTcpSocket or similar with signals and never block (in order to scale nicely)
- My main problem is to implement the WS handshake. Whoever wrote the spec was on pot and the thing is insane. Do a basic framework accepting tcp connections and handling the websocket handshake as implemented in major browsers (and without accepting invalid stuff) and you'll get your BTC (not the max, but not the min)
- The thing shouldn't crash if client connects and throw random stuff, and timeout clients nicely if they do not handshake
Let me know if you need additional details.
Jump to: