ok roger... now i understand where you coming from... confusion begins when a terminology doesnt fit to its term...
first.. you were talking about scalability but instead you were referring to feature sets of kannel... it is the capacity thing and not the features when load increases... that is what scalability is all about in telecommunications and software engineering parlance... second... you were talking about kannel cannot be controlled... you simply misunderstood the true concept of open source ideology... as the name implies.. you have all the freedom to do with the code... now if you want to add something and apply a patch back to a particular project (not only to kannel but to other projects as well)... dont blame them as they see fit what is best for their project... same thing if someone apply a patch to your project and you dont agree with it.. you simply reject it... if you dont agree with them.. you have the options to fork their project or start from scratch (as what you did)... that is what happening to open source community as you saw there were lots of projects forking into one another... thats the true concept of open source - freedom to do with the code and not controlling it... On Sat, Mar 1, 2008 at 8:06 PM, Roger Filomeno <[EMAIL PROTECTED]> wrote: > Well once you start diverging from the kannel release branch to support our > telco's unique quirks (patches), then aint it the same as building your own > gateway at the very least? > > Like i said, we forked kannel to PHP, its the same algorithms with changes > to queuing. Ofcourse we can no longer go back to kannel's main branch if the > new release becomes available. At the same time any changes we added are > categorized proprietary so we cant submit them kannel to be added back to > the branch. Actually if my memory serves me right, Dido mentioned that he > did try submitting patches to the kannel dev to be added to the main release > branch but it was rejected. Even if you read the mailing list, a lot of > people has made patches (also found a patch about weighted load balancing) > but the people maintaining kannel has rejected it as well citing numerous > philosophical design differences between the maintainer and contributors. > This is what i meant when i said Kannel cannot be fully controlled. > > On Fri, Feb 29, 2008 at 9:27 PM, Orlando Andico <[EMAIL PROTECTED]> > wrote: > > It's not that you can't fully control Kannel --- it's open source. > > > > It's that Kannel is written a certain way and is difficult to modify. > > Plus it's in C, with all the pitfalls and gotchas inherent in that > > approach. > > > > My former employer did everything in Perl. And it scaled extremely well. > > > > > > > > On Fri, Feb 29, 2008 at 5:45 PM, Roger Filomeno <[EMAIL PROTECTED]> > wrote: > > > Sorry for the rants of kannel, im not discrediting it. I just wanted to > > > point out that its not the solution in all cases especially with what > Mark > > > wanted -- a sort of SMSC-to-SMSC relay. > > > > > > As pointed out by Orly, half of the solution is out there so why not > build > > > your own than rely on something that you cannot fully control like > Kannel. > > > Surely with such requirement as Mark posted, the project should be big > and > > > surely they have the technical power to build something that do what it > > > should do than use Kannel that does only half. :D > > > > > > > > _________________________________________________ > > Philippine Linux Users' Group (PLUG) Mailing List > > [email protected] (#PLUG @ irc.free.net.ph) > > Read the Guidelines: http://linux.org.ph/lists > > Searchable Archives: http://archives.free.net.ph > > > > > > -- > -- > Roger P. Filomeno > International Project Manager > TechBiz Asia Group Pte Ltd > > http://corruptedpartition.blogspot.com/ > send MSG GODIE <YOUR MESSAGE> to 2948 > > $> who | grep -i blond | date; cd ~; unzip; touch; strip; finger; mount; > gasp; yes; uptime; umount; sleep > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > [email protected] (#PLUG @ irc.free.net.ph) > Read the Guidelines: http://linux.org.ph/lists > Searchable Archives: http://archives.free.net.ph > _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
