Thread: [Embedlets-developer] Catching up on the postings.
Status: Alpha
Brought to you by:
tkosan
Menu
▾
▴
embedlets-developer
|
From: Christopher S. <cs...@oo...> - 2003-01-29 02:16:41
|
In reviewing the postings of the last couple of weeks it appears that a solid development path has yet to be laid and the project members have not yet achieved consensus on the priorities and division of effort. This is natural for a startup project such as this. Some of the issues are sticky and contentious others are generally agreed on. May I suggest that: 1. A list of the issues/tasks be created and prioritized 2. Each task gets portioned out to one or two individuals based on skill and desire 3. The results of the efforts posted to cvs as ready 4. A discussion thread for each task is created open to the group as a whole. 5. Contentious issues can be tabled for later resolution in favor of those that can produce real results in short order. A two level list might look like: 1. Container specifications add/remove/locate methods embedlet instantiation and population life cycle RPC methods (getEmbedletPropeties, setEmbedletProperties, start, stop etc) 2. Embedlet specification container facing interface persistence interface life cycle error management 3. Event API Listener Source Methods RT thread issues 4. XML persistence and serialization Properties interface (getProperty(), setProperty()) XML schema (not necessarily enforced) parser selection and minimal requirements (SAX, DOM, unidirectional pull?) 5. Communication protocol Request/response retry recovery socket pooling and management 6. Storage (local persistence) CLDC based? Stream or database? 7. GUI specifications Java bean subclass Design paradigm 8. Web services specification http/XML envelope SOAP transport JSP/J2EE/ASP/.NET examples 9. Mobile and wireless specifications CLDC/MIDP Socket/proxy requirements parser configuration Obviously a list like this needs to be distributed amongst the developers involved, although we will all have strong opinions in some or all of the areas our efforts should be directed at generating a solid, simple specification and reference implementation that can be understood and accepted. Finally (if you have not lost interest), I would like to offer to contribute a large body of work on a implementation that embodies a number of the concepts envisioned in Embedlets. I am offering to present the API and implementation for critique, inclusion in or conversion to the Embedlets specification and/or as the basis for a reference implementation. I see this code base as a good head start that proves the concepts of Embedlets but requires conformity to a standard that will endure and be accepted by the embedded community at large. Sorry for the dissertation, I got carried away on my first posting. Christopher Smith |
|
From: Brill P. <bri...@ro...> - 2003-01-29 05:39:34
|
I've been chatting with Andrzej in private e-mail (I guess it should have gone to the list) about the XML thing... He basically filled me in on some of the stuff I missed over the holiday "break" we had, and I'm now up to speed. Anyway, no more argument from me about the XML, as when built right it won't matter. - Brill Pappin Rogue Robotics www.roguerobotics.com ----- Original Message ----- From: "Christopher Smith" <cs...@oo...> To: <emb...@li...> Sent: Tuesday, January 28, 2003 9:17 PM Subject: [Embedlets-developer] Catching up on the postings. > In reviewing the postings of the last couple of weeks it appears that a > solid development path has yet to be laid and the project members have not > yet achieved consensus on the priorities and division of effort. This is > natural for a startup project such as this. Some of the issues are sticky > and contentious others are generally agreed on. > > May I suggest that: > > 1. A list of the issues/tasks be created and prioritized > 2. Each task gets portioned out to one or two individuals based on skill and > desire > 3. The results of the efforts posted to cvs as ready > 4. A discussion thread for each task is created open to the group as a > whole. > 5. Contentious issues can be tabled for later resolution in favor of those > that can produce real results in short order. > > A two level list might look like: > > 1. Container specifications > add/remove/locate methods > embedlet instantiation and population > life cycle > RPC methods (getEmbedletPropeties, setEmbedletProperties, start, stop etc) > 2. Embedlet specification > container facing interface > persistence interface > life cycle > error management > 3. Event API > Listener > Source > Methods > RT thread issues > 4. XML persistence and serialization > Properties interface (getProperty(), setProperty()) > XML schema (not necessarily enforced) > parser selection and minimal requirements (SAX, DOM, unidirectional pull?) > 5. Communication protocol > Request/response > retry recovery > socket pooling and management > 6. Storage (local persistence) > CLDC based? > Stream or database? > 7. GUI specifications > Java bean subclass > Design paradigm > 8. Web services specification > http/XML envelope > SOAP transport > JSP/J2EE/ASP/.NET examples > 9. Mobile and wireless specifications > CLDC/MIDP > Socket/proxy requirements > parser > configuration > > Obviously a list like this needs to be distributed amongst the developers > involved, although we will all have strong opinions in some or all of the > areas our efforts should be directed at generating a solid, simple > specification and reference implementation that can be understood and > accepted. > > Finally (if you have not lost interest), I would like to offer to contribute > a large body of work on a implementation that embodies a number of the > concepts envisioned in Embedlets. I am offering to present the API and > implementation for critique, inclusion in or conversion to the Embedlets > specification and/or as the basis for a reference implementation. I see this > code base as a good head start that proves the concepts of Embedlets but > requires conformity to a standard that will endure and be accepted by the > embedded community at large. > > Sorry for the dissertation, I got carried away on my first posting. > > Christopher Smith > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Embedlets-developer mailing list > Emb...@li... > https://lists.sourceforge.net/lists/listinfo/embedlets-developer |
|
From: Ted K. <tk...@ya...> - 2003-01-29 05:47:30
|
Chris, Nice to have you on board! > Sorry for the dissertation, I got carried away on my first posting. Ha! In this list, if your post had been any shorter than it was we would have considered you to be a weakling. ;-) Actually, your suggestions have come at a good time because I think we are just now turning our attention to how we are going to organize and manage the project. Up until this point I think we have been mostly getting to know each other a little better and of course beating the snot out of each other a bit too! We have been pounding on the Embedlets idea since about mid November 2002 and one thing I think we have definitely discovered is that it is a very challenging area to attain consensus in due to its diverse nature. The good news is that most of the ideas and issues that people care about have already been submitted to the list and over the next few days (and probably through the weekend) I plan on extracting this information and placing it into a shared document so that we can start to organize and prioritize it. It sounds like you have some open source experience under your belt? If so, can you tell us a bit more about it? Also, your code base sounds interesting. Can you give us some more details about it too? Ted __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
|
From: Christopher S. <cs...@oo...> - 2003-01-29 07:30:41
|
This is my first open source development, but I have a few years of sitting in the cross fire on several enterprise software projects. The trick is to keep an open and energetic environment that allows people to express their creativity and opinions without resorting to weaponry. The one thing that is always tough to keep in perspective when two competing ideas are contentiously debated is that sometimes no decision is worse than the 'wrong' decision. -----Original Message----- From: emb...@li... [mailto:emb...@li...]On Behalf Of Ted Kosan Sent: Tuesday, January 28, 2003 9:48 PM To: emb...@li... Subject: [Embedlets-developer] Re: Catching up on the postings. Chris, Nice to have you on board! > Sorry for the dissertation, I got carried away on my first posting. Ha! In this list, if your post had been any shorter than it was we would have considered you to be a weakling. ;-) Actually, your suggestions have come at a good time because I think we are just now turning our attention to how we are going to organize and manage the project. Up until this point I think we have been mostly getting to know each other a little better and of course beating the snot out of each other a bit too! We have been pounding on the Embedlets idea since about mid November 2002 and one thing I think we have definitely discovered is that it is a very challenging area to attain consensus in due to its diverse nature. The good news is that most of the ideas and issues that people care about have already been submitted to the list and over the next few days (and probably through the weekend) I plan on extracting this information and placing it into a shared document so that we can start to organize and prioritize it. It sounds like you have some open source experience under your belt? If so, can you tell us a bit more about it? Also, your code base sounds interesting. Can you give us some more details about it too? Ted __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Embedlets-developer mailing list Emb...@li... https://lists.sourceforge.net/lists/listinfo/embedlets-developer |
|
From: James C. <ca...@vi...> - 2003-01-29 06:04:58
|
> Finally (if you have not lost interest), I would like to offer to > contribute > a large body of work on a implementation that embodies a number of the > concepts envisioned in Embedlets. Christopher.. Wow! great first post. Is this a body of work that has already been implemented 'along the lines of Embedlets' or is this work you are volunteering to do. I think what Ted will say is that you have taken the words right out of his mouth.. as a group we have only just right now 'converged' enough to present the type of implementation outline you have jump-started us with. Great work. James Caska http://www.muvium.com 'Java Bred for Embedded' > -----Original Message----- > From: emb...@li... > [mailto:emb...@li...]On Behalf Of > Christopher Smith > Sent: Wednesday, January 29, 2003 1:17 PM > To: emb...@li... > Subject: [Embedlets-developer] Catching up on the postings. > > > In reviewing the postings of the last couple of weeks it appears that a > solid development path has yet to be laid and the project members have not > yet achieved consensus on the priorities and division of effort. This is > natural for a startup project such as this. Some of the issues are sticky > and contentious others are generally agreed on. > > May I suggest that: > > 1. A list of the issues/tasks be created and prioritized > 2. Each task gets portioned out to one or two individuals based > on skill and > desire > 3. The results of the efforts posted to cvs as ready > 4. A discussion thread for each task is created open to the group as a > whole. > 5. Contentious issues can be tabled for later resolution in favor of those > that can produce real results in short order. > > A two level list might look like: > > 1. Container specifications > add/remove/locate methods > embedlet instantiation and population > life cycle > RPC methods (getEmbedletPropeties, setEmbedletProperties, > start, stop etc) > 2. Embedlet specification > container facing interface > persistence interface > life cycle > error management > 3. Event API > Listener > Source > Methods > RT thread issues > 4. XML persistence and serialization > Properties interface (getProperty(), setProperty()) > XML schema (not necessarily enforced) > parser selection and minimal requirements (SAX, DOM, > unidirectional pull?) > 5. Communication protocol > Request/response > retry recovery > socket pooling and management > 6. Storage (local persistence) > CLDC based? > Stream or database? > 7. GUI specifications > Java bean subclass > Design paradigm > 8. Web services specification > http/XML envelope > SOAP transport > JSP/J2EE/ASP/.NET examples > 9. Mobile and wireless specifications > CLDC/MIDP > Socket/proxy requirements > parser > configuration > > Obviously a list like this needs to be distributed amongst the developers > involved, although we will all have strong opinions in some or all of the > areas our efforts should be directed at generating a solid, simple > specification and reference implementation that can be understood and > accepted. > > Finally (if you have not lost interest), I would like to offer to > contribute > a large body of work on a implementation that embodies a number of the > concepts envisioned in Embedlets. I am offering to present the API and > implementation for critique, inclusion in or conversion to the Embedlets > specification and/or as the basis for a reference implementation. > I see this > code base as a good head start that proves the concepts of Embedlets but > requires conformity to a standard that will endure and be accepted by the > embedded community at large. > > Sorry for the dissertation, I got carried away on my first posting. > > Christopher Smith > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Embedlets-developer mailing list > Emb...@li... > https://lists.sourceforge.net/lists/listinfo/embedlets-developer > > |