Thursday, June 7, 2007

Is sps and x4m here to stay and how to reduce the risk?

- the team vision of developing x4m is to create Real-time shared web applications. Using extensible gecko-browsers family as base, a lot of other add-ons could be added according to current user demands.
- SPS is an application to tryout and demo the feature of x4m.
- They are constantly upgrading x4m and SPS, such as implementing file transfer capability using Google's libjingle and Gateway interaction between MSN, AIM and Yahoo!
- list of team members, click names for profile.
- SPS and x4m are distributed as .xpi files, which can be easily extracted using any unzip utility. All the implementation codes are in there. (Reducing risk if they decided to stop development)
- very interesting points on Rapid development of rich clients and browser extensions

- PROs:
- we can build TrueTalk on top of SPS as its extensions, or might as well create our own extension for firefox (need the codes to connect to gtalk)
- if we use x4m/sps, no need for intermediary servers, we only need firefox or its siblings.

- CONs:
- Only ran on gecko-based browsers.

1 comment:

Aadaam said...

Hi, I'm Adam Nemeth (from jabbermania.blogspot.com) Found your blog on technorati.

I think we should standardize the way xmpp4moz through XEP process. Would you like to join a brainstorming on this?