Changes

Jump to navigation Jump to search
1 byte added ,  22:16, 24 July 2010
m
no edit summary
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 :
  
190

edits

Navigation menu