What techniques are available to do P2P in the browser? [closed] - javascript

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
What options does a web developer currently have for implementing client-side peer-to-peer systems in the web browser? Some hypothetical examples might be a file-sharing service that bypasses the web-server after clients find eachother, or a chat service.
What I know about:
the site chatroulette uses
some flash technology as discussed
here.
And I am also aware of Opera
Unity which extends the browser
model to encompass both a client and
a server, as well as this firefox plugin which works similarly
I also just came across this blog
post related to the Joose js
framework, but am not yet sure if it
is relevant here.
Support for this kind of thing seems like it might or might not be supported by websockets in HTML5 and has been discussed here and here and here.

I recommend you to take a look at RTMFP protocol in Adobe Flash Player - it seems you can build something close to what you're asking with it.

I was looking for the same thing, this library looks apealing:
rtmfp-api/

Related

Are there any advantages to building responsive/mobile websites on a Node.js server? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I've been reading that some companies have been moving their mobile platforms to node.js servers. Just wondering what the advantages of building responsive or mobile websites on node.js would be.
Just trying to determine if node.js would be the best choice of server tech in my situation - where i build responsive websites with front end scripting for ui elements, as well as some server/db driven functionality such as blogs.
No, if you are just talking about front end development, it doesn't matter what is actually serving your assets. In fact according to a few stackoverflow posts(here, here) nginx and apache perform better for serving static assets.
A plus side to node would be to have your stack all use the same language, javascript. There are all sorts of nifty javascript build tools that are built on and distributed through npm

Developing a real time collaborative drawing system [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am interested in making a realtime collaborative drawing system similar to http://flockdraw.com/ . However I would like to only use open source tools (flockdraw uses flash and also limits the number of users) and also I will host it myself.
I have been considering writing the whole thing in Java. However I realize I am not up to date with recent advances in programming languages/libraries. What would be a good programming language/library combination to do this task?
Update. This question/answer looks very relevant.
See:
Realtime HTML5 Canvas Drawing with WebSockets, Node.JS & Socket.io - all open source
draw similar technologies to the above
node.js drawing game tutorial
The basic principles for this is generally pretty easy. Just communicate the shape that has been drawn to the other users - as you suggest. With that in mind there are a number of open source realtime web technologies that you could use.
I've seen apps like that using HTML5.
Take a look at this app. I think it can help you get started.
This kind of apps usually take advantage of HTML5 Canvas and probably HTML5 WebSockets. There are lots of libraries and tutorials out there.

Use Javascript/jQuery instead of 'traditional' technologies for GUI development [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm used to developing GUIs with C++/Qt at work, but recently dived into the Javascript/jQuery world. I think it could be easily possible to connect an existing software core via JSON-interface to a jQuery UI.
I wonder what the dis/advantages are for using jQuery as a GUI instead of building the GUI with traditional technologies like C++/Qt.
Generally there are definitely more advantages rather then disadvantages, cause you're getting a cross-platform UI, but if we are talking about the native apps you will have to use wrappers to access native functions of the os level and file structure
For mobile:
Phonegap(Cordova)
Titanium
for desktop applications there's a number of wrapper, the most common aproach right now is nodejs based app which runs a webkit instance, so yo are writing both "back" and "front" on javascript, example:
AppJs
PS
Sorry can't provide links, don't have enough reputation

Real Time : Websockets vs Comet [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
i have a few questions about real time applications.
Comet vs Websockets, what is better? For example checking the online users, chat etc.
How does running any of these processes (comet server, websockets) affect normal server functions performance (Page load, php, operating with databases)?
How can i actually install websockets / comet to my hosted server and not just having it on localhost.
Im sorry if some of these questions are stupid, but im quite new to this, so i have to start somewhere :)
Once again, this is a question that is only answered by "it depends on what you're doing". Also, a simple SO and/or Google search will give you several results that I suggest you should read for a better in-depth view.
Both techniques will deliver data "real time", and both can be used to check online users, check etc. Also, Comet is an umbrella term and there are many "Comet Servers" that use WebSockets as the transport mechanism when possible. Comet servers don't just use AJAX, XHR Long-Polling, Forever-Frame etc. They now use WebSockets and fallback to other transport mechanisms where required.
Depending on what kind of back-end technique you're using, ASP.NET SignalR is pretty awesome too.

Can you help me with framework choice? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm thinking about developing an app which will make a strong use of geolocation (mongodb will be my choice), and strong upload of photos (and viewing too).
I was just wondering if you could help me with framework election. I've been using node.js for months and I'm very comfortable with it, but because of its one-process nature, will it be bad for locking when uploading big photos?
The other solution I'm working on is rails.
Which one will you choose? Any other ?
Thanks
With Streaming you can support more then one client during a upload, since the upload will be broken into different parts. I sure expressjs has some good streaming examples.
... but because of its one-process nature, will it be bad for locking when uploading big photos?
Take a look at the cluster module, this should help with leveraging more cores. In fact one of the node.js clients on the front page are these guys: Transloadit who focus on handling images.
I'm thinking about developing an app which will make a strong use of geolocation (mongodb will be my choice)...
I've done a lot of work with MongoDB and I recommend reading up on the limitations of MongoDB's geo-location tools. The product does provide some functionality, but it does not match the features of Postgres. You will want to ensure that MongoDB covers all of the features you require before beginning.

Categories