insite messaging system input?

bitmap or ianmcorvidae: After some discussion with kuno and freso, I am
interested in implementing the insite messaging/notification system. 

I previously developed a in-app backend messaging/notification system for a
startup (called Clicle) in node.js. 

I have come to an understanding that XMPP is not high on priority list . And
from what the community envisions is a messaging system similar to what is
seen in different web forums. I developed the previous system using the std
combo of node.js+socket.io.

Probably a overkill for this project if we don't need a lot of real time
capabilities but nevertheless the node.js+socket.io stack wins anytime over
other stacks because of the speed of development and easy maintainability.
It's std java script. 

Is it okay if I implement the system in node.js + socket.io? Previous
experience would help me tremendously in avoiding a lot of pitfalls thus
producing a higher quality system
 
Also I have been looking through the source code. It's definitely doable in
node.js with plugging into the perl parts totally possible. There are
existing modules for node.js which can bind with perl methods but they are
slightly outdated. I'll have to hack on that if something ends up being
incomplete. Adds a little bit more work but not that will kill the project.

If I'm right I have to plug into only two parts of the perl system -
authenticaion and the user interface. everything else can be handled by
node.js



--
View this message in context: http://musicbrainz.1054305.n4.nabble.com/insite-messaging-system-input-tp4672579.html
Sent from the MusicBrainz - Development mailing list archive at Nabble.com.