jaredhanson / jaredhanson/junction
How should I implement a keep-alive ping mechanism for an external component
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 106
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
I have written a full functional framework with a browser client using pure JavaScript and Strophe.js library to connect through BOSH to a OpenFire XMPP server talking to an "external component" written in NodeJS with junction.
Everything is working OK but the component is dissapearing from the OpenFire external components list (in admin web page) after a timeout of 10 minutes or so of inactivity. Probably this is a normal behaviour but:
- is there a chance to raise this time limit?
- how should I implement something like a keep-alive ping mechanism to make the component persistent for a very long time?
Thanks,
Constantin Teodorescu
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how junction represents and maintains an external component connection, then compare that behavior with OpenFire's external-component timeout and the BOSH connection described in the issue. The issue names no repository files or tests, so the scope and completion criteria would need to be established before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100