Menu
▾
▴
convey-developers
|
From: Scott L. <sco...@ho...> - 2003-08-05 05:53:15
|
You can count me in. >From: "Andy Ames" <ag...@sb...> >Reply-To: con...@li... >To: <con...@li...> >Subject: [convey-developers] wxjab module via wxxml >Date: Mon, 4 Aug 2003 02:07:42 -0700 > >First jabber message using wxjab! > >I added the wxjab module to our repository. It uses the wxXml module to >stream XML in and out of a socket connection. > >The API is very basic at this point. But you can login (with a plain text >password) and send messages across the jabber network. > >Next, support for digest authentication using SHA and the ability to >receive >and parse incoming messages. > >Anyway, we're really close (about 5 days) from having a working jabber API >in C++. I have to admit, though, that wxjab and wxxml are probably a bit >buggy, their lacking robust error handling, and only support the US-ASCII >subset of UTF-8. > >I'd like to know if either of you would like to volunteer to maintain the >wxxml module. We can work on it together, but I'd like someone to be >responsible for seeing that the desired improvements actually happen. Even >if this means I get assigned to 95% of the code changes, that's fine. I'm >throwing 20 hours a week at Convey currently, so that would not be a >problem. I would rather not have to do the management of the changes, so I >can charge ahead with wxjab. > >What this role means, is the person would learn the ins and outs of XML in >general. They would become familiar with the XML spec so they can reference >it when necessary. Then, this person would decide, based on inputs from the >others, what features are important to put into the wxxml module. This >person would pour over the bugs and feature requests regarding wxxml and >filter them as necessary. > >G'night. > >Andy > > > >------------------------------------------------------- >This SF.Net email sponsored by: Free pre-built ASP.NET sites including >Data Reports, E-commerce, Portals, and Forums are available now. >Download today and enter to win an XBOX or Visual Studio .NET. >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 >_______________________________________________ >convey-developers mailing list >con...@li... >https://lists.sourceforge.net/lists/listinfo/convey-developers _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail |
|
From: Ed B. <edb...@ca...> - 2003-08-08 18:11:35
|
I would like to be responsible for the wxxml module. Ed On Wednesday, August 6, 2003, at 07:45 PM, Andy Ames wrote: Okay, you both are interested in taking a module. Do you guys want to choose who gets wxxml and who gets wxjab. I'll be ready to turn over wxjab by the end of this weekend. Andy -----Original Message----- From: con...@li... [mailto:con...@li...]On Behalf Of Scott Luan Sent: Monday, August 04, 2003 10:53 PM To: con...@li... Subject: Re: [convey-developers] wxjab module via wxxml You can count me in. From: "Andy Ames" <ag...@sb...> Reply-To: con...@li... To: <con...@li...> Subject: [convey-developers] wxjab module via wxxml Date: Mon, 4 Aug 2003 02:07:42 -0700 First jabber message using wxjab! I added the wxjab module to our repository. It uses the wxXml module to stream XML in and out of a socket connection. The API is very basic at this point. But you can login (with a plain text password) and send messages across the jabber network. Next, support for digest authentication using SHA and the ability to receive and parse incoming messages. Anyway, we're really close (about 5 days) from having a working jabber API in C++. I have to admit, though, that wxjab and wxxml are probably a bit buggy, their lacking robust error handling, and only support the US-ASCII subset of UTF-8. I'd like to know if either of you would like to volunteer to maintain the wxxml module. We can work on it together, but I'd like someone to be responsible for seeing that the desired improvements actually happen. Even if this means I get assigned to 95% of the code changes, that's fine. I'm throwing 20 hours a week at Convey currently, so that would not be a problem. I would rather not have to do the management of the changes, so I can charge ahead with wxjab. What this role means, is the person would learn the ins and outs of XML in general. They would become familiar with the XML spec so they can reference it when necessary. Then, this person would decide, based on inputs from the others, what features are important to put into the wxxml module. This person would pour over the bugs and feature requests regarding wxxml and filter them as necessary. G'night. Andy ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers |
|
From: Andy A. <ag...@sb...> - 2003-08-08 19:25:25
|
Okay, wxxml to Ed; wxjab to Scott. Today, I'm going to do one last round of documenting the wxxml mod. I'll include known issues, bugs and todo items. I'll do the same with wxjab over the weekend. Scott, I'll make sure you have write access to the repository. Andy -----Original Message----- From: con...@li... [mailto:con...@li...]On Behalf Of Ed Braunhut Sent: Friday, August 08, 2003 11:12 AM To: con...@li... Subject: Re: [convey-developers] wxjab module via wxxml I would like to be responsible for the wxxml module. Ed On Wednesday, August 6, 2003, at 07:45 PM, Andy Ames wrote: Okay, you both are interested in taking a module. Do you guys want to choose who gets wxxml and who gets wxjab. I'll be ready to turn over wxjab by the end of this weekend. Andy -----Original Message----- From: con...@li... [mailto:con...@li...]On Behalf Of Scott Luan Sent: Monday, August 04, 2003 10:53 PM To: con...@li... Subject: Re: [convey-developers] wxjab module via wxxml You can count me in. From: "Andy Ames" <ag...@sb...> Reply-To: con...@li... To: <con...@li...> Subject: [convey-developers] wxjab module via wxxml Date: Mon, 4 Aug 2003 02:07:42 -0700 First jabber message using wxjab! I added the wxjab module to our repository. It uses the wxXml module to stream XML in and out of a socket connection. The API is very basic at this point. But you can login (with a plain text password) and send messages across the jabber network. Next, support for digest authentication using SHA and the ability to receive and parse incoming messages. Anyway, we're really close (about 5 days) from having a working jabber API in C++. I have to admit, though, that wxjab and wxxml are probably a bit buggy, their lacking robust error handling, and only support the US-ASCII subset of UTF-8. I'd like to know if either of you would like to volunteer to maintain the wxxml module. We can work on it together, but I'd like someone to be responsible for seeing that the desired improvements actually happen. Even if this means I get assigned to 95% of the code changes, that's fine. I'm throwing 20 hours a week at Convey currently, so that would not be a problem. I would rather not have to do the management of the changes, so I can charge ahead with wxjab. What this role means, is the person would learn the ins and outs of XML in general. They would become familiar with the XML spec so they can reference it when necessary. Then, this person would decide, based on inputs from the others, what features are important to put into the wxxml module. This person would pour over the bugs and feature requests regarding wxxml and filter them as necessary. G'night. Andy ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers |
|
From: Andy A. <ag...@sb...> - 2003-08-09 02:18:13
|
Ed, The wxxml mod is officially yours. Check out of CVS: cvs -d:ext:use...@cv...:/cvsroot/convey co wxxml (I find it easiest to do this check out right next to all my other Convey repository checkouts.) There's a README and BUILD file at the root that will help you navigate the project. Currently, there's only a build setup for MSVC. There's no Makefile or autoconf setup. We need to do this to make it easier for anyone to build it. Until then, we can setup a CodeWarrior or Project Builder project for building the library. Then, commit these projects to CVS. That way, you'll be able to do stuff with the library now. Andy |
|
From: Andy A. <ag...@sb...> - 2003-08-09 02:29:19
|
Scott, Do you have a sourceforge account I can use to add you to Convey? Can you create one and send me the username? Andy |
|
From: Andy A. <ag...@sb...> - 2003-08-09 20:38:03
|
I reorganized the sourceforge project.
We now have tasks, but only under the wxXml subproject. Items on the task
list are items that will be implemented. Also, in the wxxml source docs, I
referenced the task # from the appropriate class or method using the @todo
tag. See any of the wxXml headers for an example.
The Bug and Feature Request trackers now have the following Categories:
Convey Java
wxConvey
wxConvey : wxXml
wxConvey : wxJab
They're self-explanatory.
So, Ed, you may have gotten a flood of messages regarding tracker item
changes. That's what this is all about. I have items with the "wxConvey :
wxXml" Category automatically getting assigned to you, Ed.
They way I've been conceptualizing this whole process is like this:
1) Tasks
The subproject owner is responsible for creating and managing tasks in their
subproject, as well as assigning tasks (assuming of course the person they
assign a task to agrees). Anyone can add comments to a task to give their
feedback or insight.
I imagine, though, that the discussions will occur on this mailing list, and
then the conclusions get pasted into the task by the subproject owner.
Each Task will also be referenced from the source code doc "@todo" items.
This may not be necessary, but it certainly helps remind us of upcoming
changes when we're browsing the code.
2) Bugs
Anyone can submit bug reports on a subproject. The subproject owner is
ultimately the person who determines if the bug really is a bug, and if and
when it will be fixed. Again, the subproject owner can leverage any other
developer's time and resources to accomplish this.
Each bug that is determined to be valid by the subproject owner will also be
referenced from the revelant source docs using the "@bug" tag. This can be
done whether or not the subproject owner intends to fix the bug.
3) Feature Requests
Anyone can submit these. The subproject owner manages these items through
their lifecycle like they do with bugs.
Feature Requests would be the place where developers make suggestions to the
subproject owner regarding their subproject.
Feature Requests, once accepted by the subproject owner, are turned into
task items.
4) Developers Mailing List
This, of course, is where most of the discussions begin. Also, many
dicscussions from here will be filtered down into a task, bug, or feature
request, as necessary.
5) Conclusion
There's a hierarchy of content flow:
--- Mailing List
|
--- Bug
| |
| ---Task
|
--- Feature Request
|
---Task
Content flows from the root to a child. At any stage, the content may be
rejected as being inconsequential. Before entering the Task node, the issue
gets the subproject owner's full approval.
Of course, this is somewhat simplified, since content can be generated
offline (verbal discussions) or by non-team members submitting items. BTW,
the only non-team members likely to submit something are other developers
using our product/APIs in some way. Convey client users, OTOH, are likely to
want something a little simpler. Ed's idea was to have a bug report dialog
box in Convey. This could send a message (via Jabber) to some place
(chatroom?) where we pick it up and filter it down or content flow
hierarchy.
Anyway, sound good? I think this works for now. When we start bringing on
more developers, we can get more specific about this process.
Andy
|
|
From: Ed B. <edb...@ca...> - 2003-08-10 19:26:05
|
Thanks, Andy. Comments below... On Sat, 9 Aug 2003 13:37:48 -0700 "Andy Ames" <ag...@sb...> wrote: > I reorganized the sourceforge project. > > We now have tasks, but only under the wxXml subproject. > Items on the task > list are items that will be implemented. Also, in the > wxxml source docs, I > referenced the task # from the appropriate class or > method using the @todo > tag. See any of the wxXml headers for an example. > > The Bug and Feature Request trackers now have the > following Categories: > > Convey Java > wxConvey > wxConvey : wxXml > wxConvey : wxJab > > They're self-explanatory. Yes they are. Nice organizing. > > They way I've been conceptualizing this whole process is > like this:> > 1) Tasks > > The subproject owner is responsible for creating and > managing tasks in their > subproject, as well as assigning tasks (assuming of > course the person they > assign a task to agrees). Anyone can add comments to a > task to give their > feedback or insight. > > I imagine, though, that the discussions will occur on > this mailing list, and > then the conclusions get pasted into the task by the > subproject owner. > > Each Task will also be referenced from the source code > doc "@todo" items. > This may not be necessary, but it certainly helps remind > us of upcoming > changes when we're browsing the code. > > 2) Bugs > > Anyone can submit bug reports on a subproject. The > subproject owner is > ultimately the person who determines if the bug really is > a bug, and if and > when it will be fixed. Again, the subproject owner can > leverage any other > developer's time and resources to accomplish this. > > Each bug that is determined to be valid by the subproject > owner will also be > referenced from the revelant source docs using the "@bug" > tag. This can be > done whether or not the subproject owner intends to fix > the bug. > > 3) Feature Requests > > Anyone can submit these. The subproject owner manages > these items through > their lifecycle like they do with bugs. > > Feature Requests would be the place where developers make > suggestions to the > subproject owner regarding their subproject. > > Feature Requests, once accepted by the subproject owner, > are turned into > task items. > > 4) Developers Mailing List > > This, of course, is where most of the discussions begin. > Also, many > dicscussions from here will be filtered down into a task, > bug, or feature > request, as necessary. > > 5) Conclusion > > There's a hierarchy of content flow: > > --- Mailing List > | > --- Bug > | | > | ---Task > | > --- Feature Request > | > ---Task > > Content flows from the root to a child. At any stage, the > content may be > rejected as being inconsequential. Before entering the > Task node, the issue > gets the subproject owner's full approval. > > Of course, this is somewhat simplified, since content can > be generated > offline (verbal discussions) or by non-team members > submitting items. BTW, > the only non-team members likely to submit something are > other developers > using our product/APIs in some way. Convey client users, > OTOH, are likely to > want something a little simpler. Ed's idea was to have a > bug report dialog > box in Convey. This could send a message (via Jabber) to > some place > (chatroom?) where we pick it up and filter it down or > content flow > hierarchy. > Yes, I haven't finished this way of bug reporting and am wondering if this would be too much to add at this late date. > Anyway, sound good? I think this works for now. When we > start bringing on > more developers, we can get more specific about this > process. It sounds fine. We don't really have that many developers so the process probably only needs clarifying on a as-needed basis. When we find ourselves spending alot of time clarifying the process, then we should sit down and spend a bit more time on formalizing the process. Thanks, Andy. |
|
From: Andy A. <ag...@sb...> - 2003-08-07 02:46:07
|
Okay, you both are interested in taking a module. Do you guys want to choose who gets wxxml and who gets wxjab. I'll be ready to turn over wxjab by the end of this weekend. Andy -----Original Message----- From: con...@li... [mailto:con...@li...]On Behalf Of Scott Luan Sent: Monday, August 04, 2003 10:53 PM To: con...@li... Subject: Re: [convey-developers] wxjab module via wxxml You can count me in. >From: "Andy Ames" <ag...@sb...> >Reply-To: con...@li... >To: <con...@li...> >Subject: [convey-developers] wxjab module via wxxml >Date: Mon, 4 Aug 2003 02:07:42 -0700 > >First jabber message using wxjab! > >I added the wxjab module to our repository. It uses the wxXml module to >stream XML in and out of a socket connection. > >The API is very basic at this point. But you can login (with a plain text >password) and send messages across the jabber network. > >Next, support for digest authentication using SHA and the ability to >receive >and parse incoming messages. > >Anyway, we're really close (about 5 days) from having a working jabber API >in C++. I have to admit, though, that wxjab and wxxml are probably a bit >buggy, their lacking robust error handling, and only support the US-ASCII >subset of UTF-8. > >I'd like to know if either of you would like to volunteer to maintain the >wxxml module. We can work on it together, but I'd like someone to be >responsible for seeing that the desired improvements actually happen. Even >if this means I get assigned to 95% of the code changes, that's fine. I'm >throwing 20 hours a week at Convey currently, so that would not be a >problem. I would rather not have to do the management of the changes, so I >can charge ahead with wxjab. > >What this role means, is the person would learn the ins and outs of XML in >general. They would become familiar with the XML spec so they can reference >it when necessary. Then, this person would decide, based on inputs from the >others, what features are important to put into the wxxml module. This >person would pour over the bugs and feature requests regarding wxxml and >filter them as necessary. > >G'night. > >Andy > > > >------------------------------------------------------- >This SF.Net email sponsored by: Free pre-built ASP.NET sites including >Data Reports, E-commerce, Portals, and Forums are available now. >Download today and enter to win an XBOX or Visual Studio .NET. >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 >_______________________________________________ >convey-developers mailing list >con...@li... >https://lists.sourceforge.net/lists/listinfo/convey-developers _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ convey-developers mailing list con...@li... https://lists.sourceforge.net/lists/listinfo/convey-developers |
|
From: Andy A. <ag...@sb...> - 2003-08-07 03:51:10
|
Well, plans for whiteboarding support directly in jabber have been toyed with for some time. Here's some relevant URLs: Jabber Enhacement Proposal: Whiteboarding JIG http://www.jabber.org/jeps/jep-0010.html Collaborative Imaging (Whiteboarding via Streaming XPM) http://docs.jabber.org/draft-proto/html/sxpm.html SVG Whitreboard v0.1 http://oid.jabber.org/?oid=1025 Jabberzilla Whiteboard http://jabberzilla.mozdev.org/ The first URL is a request for a Jabber Interest Group to be set up to identify the requirements and data format of such a protocol. From being on the mailing list, it doesn't seem very hard to become a member of the Jabber Software Foundation (JSF). I believe membership is a prereq to becoming a member of a JIG. Thought you'd like to know. Andy |
|
From: Andy A. <ag...@sb...> - 2003-08-07 04:00:49
|
First, there isn't much timstamp handling in core Jabber. There is a Jabber
extension called Entity Time (JEP-0090) that allows an entity to query the
time of another entity. It looks like this:
SENT: <iq type='get'
from='ro...@mo.../orchard'
to='ju...@ca.../balcony'
id='time_1'>
<query xmlns='jabber:iq:time'/>
</iq>
RECV: <iq type='result'
from='ju...@ca.../balcony'
to='ro...@mo.../orchard'
id='time_1'>
<query xmlns='jabber:iq:time'>
<utc>20020910T17:58:35</utc>
<tz>MDT</tz>
<display>Tue Sep 10 12:58:35 2002</display>
</query>
</iq>
However, I do not see anyway of accounting for lag time in the iq query
message itself.
Also, conferencing does NOT reliably store the history on the server. It
stores some history and when a client connects, the recent history of
messages is forwarded to the new client to give them some context of the
current discussion. However, this is NOT part of the Jabber spec and is
server implementation dependant.
That's not good for us. Anyway, it's looking like we are on our own with a
server implementation. Yes, we can create adhoc clients (such as session
"initiator") and other such solutions. But, they are contrary to the design
(and spirit) of Jabber being server-centric.
To really do what we want, we have to take control. At first, 2 years ago,
this scared us. But now, I'm not at all intimidated by writing our own
Jabber extension.
This brings other things with it. Like the fact that we'll have to run our
own server if we want people to use it.
Andy
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X