Hi Alexander,
Finally today we announced our intention to open source BrowserPlus. What this would mean for this specific idea is that we could start a project around it.
Within the next couple months we'll have our API and documentation around the implementation of services available, and we'd love to hack this idea out together, out it the open. If nothing else we could flesh some ideas about an API that could expose p2p communications to javascript.
very best,
lloyd
Sorry for the slow response.
Have been playing around with services, have a couple of questions.
* Why the need for bp_require? It looks like it needs an absolute path from the service folder too.
* Is bp.complete part of the async api. If so, that's really cool! This async api makes it really easy to add bonjour integration. Can I call it multiple times?
* Can I return Ruby objects?
I'm thinking a Bonjour api would look like this:
PlusJour.list(service_name, timeout=3)
PlusJour.register(service_name, name, port, text_record)
This sort of thing is currently really hard to test with the current workflow (especially since it deletes your code if you get anything wrong!), but I'm sure that'll change with the published api.
Can you PM me if there's some sort of private beta for that api.
Thanks,
Alex