Difference between revisions of "GSoC05 FAQ"

From XMPP WIKI
Jump to navigation Jump to search
m
m
 
Line 29: Line 29:
  
 
=== What is my project about ? ===
 
=== What is my project about ? ===
me : My project is about writing a lingo library for a jabber client, supporting most of the XMPP/Jabber core protocol and as many JEPs as I can. JEPs aren't, however, a mandatory feature in the library (altought there are many JEPs that I will try to implement). I am going to use a xml parser library in lingo to handle the protocol and a TCP/IP shockwave Xtra (Plugin) to connect to the jabber server.
+
me : My project is about writing a lingo library for a jabber client, supporting most of the XMPP/Jabber core protocol and as many XEPs as I can. XEPs aren't, however, a mandatory feature in the library (altought there are many XEPs that I will try to implement). I am going to use a xml parser library in lingo to handle the protocol and a TCP/IP shockwave Xtra (Plugin) to connect to the jabber server.
  
 
jsf :
 
jsf :
Line 41: Line 41:
 
me : I think I should start coding the "Instant Messaging and Presence Protocol", since it will bring me some quick results and I will have a working client with it (meaning that I will be able to connect/login/send messages/ask for subscriptions/loading rosters/setting presece/etc ... ). Besides, the "Instat Messaging and Presence Protocol" seems to me much more easy to understand,since it is much closer to what I understand about IM.
 
me : I think I should start coding the "Instant Messaging and Presence Protocol", since it will bring me some quick results and I will have a working client with it (meaning that I will be able to connect/login/send messages/ask for subscriptions/loading rosters/setting presece/etc ... ). Besides, the "Instat Messaging and Presence Protocol" seems to me much more easy to understand,since it is much closer to what I understand about IM.
  
After that, I should analyse (with JSF) what would be more important : coding the "Core Protocol" or coding the JEPs. Coding the JEPs whould be pretty straightforwared, and would bring me some nice results too ... I still don't understand the need to code the "Core Protocol", but since it is called "Core" it should be VERY important ...  
+
After that, I should analyse (with JSF) what would be more important : coding the "Core Protocol" or coding the XEPs. Coding the XEPs whould be pretty straightforwared, and would bring me some nice results too ... I still don't understand the need to code the "Core Protocol", but since it is called "Core" it should be VERY important ...  
  
 
jsf :
 
jsf :
Line 47: Line 47:
 
=== What is considered "job completed" ? ===
 
=== What is considered "job completed" ? ===
 
me : a lingo library and a working demo. The real question is : wich features for the library are mandatory and wich aren't ? Perhaps the ones that are marked as MUST in the protocols ...
 
me : a lingo library and a working demo. The real question is : wich features for the library are mandatory and wich aren't ? Perhaps the ones that are marked as MUST in the protocols ...
* According to this document [http://www.jabber.org/jeps/jep-0073.html JEP0073], "Core Protocol" is required ...
+
* According to this document [http://xmpp.org/extensions/xep-0073.html XEP-0073], "Core Protocol" is required ...
 
jsf :
 
jsf :
  
Line 56: Line 56:
  
 
=== What else could I do ? ===
 
=== What else could I do ? ===
me : JEPs, JEPs and JEPs. Since there are so many, I should start coding the most usefull/popular ones.
+
me : XEPs, XEPs and XEPs. Since there are so many, I should start coding the most usefull/popular ones.
  
 
jsf :
 
jsf :
Line 71: Line 71:
  
 
=== What points I still don't know to handle ? ===
 
=== What points I still don't know to handle ? ===
me : I still don't know how I am going to handle TLS and SASL in my work ... any ideas ? Is it that important (meaning that it is more important than getting more JEPs working) ?
+
me : I still don't know how I am going to handle TLS and SASL in my work ... any ideas ? Is it that important (meaning that it is more important than getting more XEPs working) ?
  
 
jsf :  
 
jsf :  
Line 77: Line 77:
 
SASL is required by the xmpp rfc, which means that if you want your implementation to claim that it uses xmpp, then you have to implement SASL. However, TLS is optional. Its a really really good idea, but it is not strictly required.  - [[User:Zion|Zion]]
 
SASL is required by the xmpp rfc, which means that if you want your implementation to claim that it uses xmpp, then you have to implement SASL. However, TLS is optional. Its a really really good idea, but it is not strictly required.  - [[User:Zion|Zion]]
  
=== Whick JEPs should I start working with ? ===
+
=== Whick XEPs should I start working with ? ===
 
me :
 
me :
  

Latest revision as of 22:16, 24 July 2010

FAQ

This FAQ is supposed to be a knowlodge sharing between 
me and my mentoring organization, JSF. If you are from JSF 
or you know any answer to these questions, please, let me 
know and complete the page ! thanks !

Users Documentation

Is there a tutorial for this library ?

Yes, you can find it in the main page.

SOC Documentation

What did I already do ?

me :

  • Read both of the XMPP protocols specification
  • Found a way to connect the shockwave movie to the jabber server (Multiuser Xtra)
  • Found a way to parse XML streams (xml.parser library)
  • Started coding some simple streams negotiation with ONLY basic flows (from the "XMPP IM and Presence Protocol")
    • Able to login
    • Able to set presence
    • Able to get roster
    • Able to send and receive messages
    • Able to handle subscription
    • Able to deal with some simple error messages


jsf :


What is my project about ?

me : My project is about writing a lingo library for a jabber client, supporting most of the XMPP/Jabber core protocol and as many XEPs as I can. XEPs aren't, however, a mandatory feature in the library (altought there are many XEPs that I will try to implement). I am going to use a xml parser library in lingo to handle the protocol and a TCP/IP shockwave Xtra (Plugin) to connect to the jabber server.

jsf :

What is my project not about ?

me : My project is not about writing a full featured client, but a library. Anyway, I should get one running client to demonstrate the client library, but it shouldn't be the main task of my work.

jsf :

Where should I start ?

me : I think I should start coding the "Instant Messaging and Presence Protocol", since it will bring me some quick results and I will have a working client with it (meaning that I will be able to connect/login/send messages/ask for subscriptions/loading rosters/setting presece/etc ... ). Besides, the "Instat Messaging and Presence Protocol" seems to me much more easy to understand,since it is much closer to what I understand about IM.

After that, I should analyse (with JSF) what would be more important : coding the "Core Protocol" or coding the XEPs. Coding the XEPs whould be pretty straightforwared, and would bring me some nice results too ... I still don't understand the need to code the "Core Protocol", but since it is called "Core" it should be VERY important ...

jsf :

What is considered "job completed" ?

me : a lingo library and a working demo. The real question is : wich features for the library are mandatory and wich aren't ? Perhaps the ones that are marked as MUST in the protocols ...

  • According to this document XEP-0073, "Core Protocol" is required ...

jsf :

Wich are the basic features ?

me : I understand that the basic features are "Instant Messaging and Presence Protocol". The "Core Protocol" should be a basic feature too, but I haven't read it all ...

jsf :

What else could I do ?

me : XEPs, XEPs and XEPs. Since there are so many, I should start coding the most usefull/popular ones.

jsf :

How is JSF going to evaluate my work ?

me : By seeing the working demo/example, and reading the source code.

jsf :

Where can I get help ?

me : jabber.org, jadmin mailing list and Peter St Andre !

jsf :

What points I still don't know to handle ?

me : I still don't know how I am going to handle TLS and SASL in my work ... any ideas ? Is it that important (meaning that it is more important than getting more XEPs working) ?

jsf :

SASL is required by the xmpp rfc, which means that if you want your implementation to claim that it uses xmpp, then you have to implement SASL. However, TLS is optional. Its a really really good idea, but it is not strictly required. - Zion

Whick XEPs should I start working with ?

me :

jsf :

Back