FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Mango & Tango

 
Post new topic   Reply to topic     Forum Index -> Mango
View previous topic :: View next topic  
Author Message
kris



Joined: 27 Mar 2004
Posts: 1494
Location: South Pacific

PostPosted: Fri Feb 02, 2007 11:27 am    Post subject: Mango & Tango Reply with quote

What's going on with Mango, now that Tango is on the scene?

Tango contains a significant subset of Mango. The rest of Mango is entirely independent and will remain so. We're talking all the server software, clustering, Servlet engine, Sax engine, etc etc. Each of these have been 'adjusted' to operate atop of Tango, so the two projects are fully aligned.

At this time, we're deciding whether to move this updated Mango code into a new repository, or simply (*cough*) branch the original Mango Tree and use Trunk to contain the updated code only. This would have been worked out before, but focus has been elsewhere: I'm sure you can understand Smile

Then there's the question of phobos compatability. Mango is compatible with phobos (via a -version) whilst Tango is not intended to be. Thus, for those folks using phobos, the original Mango Tree is the right place to come to. For those moving to Tango instead, you'll find there's an immediate comfort level with a large chunk of the Tango functionality. The package layout/hierarchy is a little different, but the capabilities are almost identical for a given package.

Three takeaway items:

1) the high level Mango entities have been made fully compatible with Tango, and can be used alongside it without issue. This aspect of Mango code makes it "Tango Certified" if you like. These Tango versions currently reside elsewhere; they are not checked into the Mango SVN.

2) phobos users should continue to use the original Mango code. Those looking to use Tango instead will find a familiar set of Mango capabilities.

3) Tango itself will avoid adopting lots of interesting but perhaps ancilliary code as core functionality. This is intended to retain a sense of coherence and compactness within Tango, whilst leaving the door open for competing add-ons (such as alternate server implementations).

What do you think? Should we place the Tango certified code in a seperate project, or branch the current Mango codebase, and place the Tango compatible code here instead? And, how should the Phobos compatability issue be resolved for Mango?
Back to top
View user's profile Send private message
kris



Joined: 27 Mar 2004
Posts: 1494
Location: South Pacific

PostPosted: Sun Feb 04, 2007 11:50 am    Post subject: Reply with quote

It seems that the best approach is to branch the existing code base, and migrate to a Tango compatible layer. The existing code would remain accessible via the branch, and be maintained there. Phobos support would be handled via the branch.

The wiki page would change to reflect the pared-down Mango library, with a link to a pre-Tango page representing the branched code-base.

At that point Mango becomes a Tango compatible library, focused upon server oriented functionality (servlets, SAX, http, etc). Most of the rest is rolled into Tango instead.

Sound good?
Back to top
View user's profile Send private message
teqdruid



Joined: 11 May 2004
Posts: 390
Location: UMD

PostPosted: Sun Feb 04, 2007 12:34 pm    Post subject: Reply with quote

kris wrote:
It seems that the best approach is to branch the existing code base, and migrate to a Tango compatible layer. The existing code would remain accessible via the branch, and be maintained there. Phobos support would be handled via the branch.

The wiki page would change to reflect the pared-down Mango library, with a link to a pre-Tango page representing the branched code-base.

At that point Mango becomes a Tango compatible library, focused upon server oriented functionality (servlets, SAX, http, etc). Most of the rest is rolled into Tango instead.

Sound good?


Sounds OK to me... Although it's always sorta been for server stuff, I dunno if we want to keep Mango labeled that way, though. For instance, SAX and an XML_RPC client aren't necessarily server stuff- clients need them to talk to the server. Perhaps communication-oriented is better? No, that would preclude cache stuff... I dunno- it's a pretty minor point.

Please let us know when you do it! I just finished up the SAX port and I'm anxious to get it in SVN.

~John
Back to top
View user's profile Send private message Send e-mail AIM Address
kris



Joined: 27 Mar 2004
Posts: 1494
Location: South Pacific

PostPosted: Mon Feb 05, 2007 6:50 pm    Post subject: Reply with quote

OK .. the first part of the move is done.

Prior Mango codebase is now in branches/v2.1, and the trunk now contains a set of Tango-compatible code only. Added a place-holder for the XML packages, and for related examples. Clustering will be added shortly, once it is tested a bit further.

- Kris
Back to top
View user's profile Send private message
kris



Joined: 27 Mar 2004
Posts: 1494
Location: South Pacific

PostPosted: Tue Feb 20, 2007 5:40 pm    Post subject: Reply with quote

This is all basically done with now ... the Mango trunk requires the Tango library to operate, and is now considered to be an (important) extension of that library.

Phobos compatible code resides in the branch noted above.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic     Forum Index -> Mango All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group