January 19, 2012

Damien Katz

Couchbase Meetup at new HQ

Join us Thursday January 19 at 6:30 PM at our brand new Headquarters (aka Fort Awesome). Join and RSVP here.

by Damien Katz at January 19, 2012 02:39 AM

January 11, 2012

Damien Katz

Why Couchbase?

So apparently my last entry ruffled some feathers, so maybe I should explain why I think Couchbase is the future?

Simple Fast Elastic.

That's pretty much it. We make it very simple to get started, we are extremely fast (and getting faster), and we really are "web scale", with the ability to add and remove machines from a cluster to rapidly scale your capacity to your workload.

The Membase product was very fast and scalable, but a bit too simple, with no reporting capability or cross-datacenter replication capability.

The CouchDB product has a lot of features, but is too slow, unable to keep up with high loads and inability scale-out on it's own.

The combination of the 2 will hit a sweet spot to allow developers to quickly get their apps up and running, along with the reliability, speed and low cost that make running it in production cheap and worry free.

Our 2.0 product is coming soon, adding CouchDB style views and reporting with a nifty trick for extremely fast failover while maintaining full coherency with the underling distributed data storage (we are calling it our B-Superstar index). We'll of course have lighting fast reads (same as Memcached) but also very fast durable writes. For 2kb docs, we are currently getting sustained random insert/updates rates of 25k writes/sec, fully durable, with compaction in background so it can go all day and all night. We've got some more write work coming soon which we are hoping will give us another performance boost too before 2.0. Stay tuned.

And so right now the focus is on the features and customers that pay, a thing that allow us to build a real sustainable business. And that's REAL DAMN IMPORTANT. It's not enough to build some cool technology, not enough to build a community of excited technologist. You need to cross the chasm and build a real business. A business that provides support, training, documentation and of course a reliable product. A business you can call up when you have difficultly upgrading from an old version, or are getting some weird error you've never seen before at 3am. A business you know will be around to support you for years to come.

And so while we focus on the features and customers that most quickly make us a viable business (and it's growing fast), we are still looking to build the features and technology to expand our use cases and, get customers and developers excited. Future versions are planned to have full CouchDB compatible replication technology, with the ability to support all sorts of mobile and embedded databases, such as our new TouchDB projects for iOS and Android. So with Couchbase you can have fast, scalable database in the cloud that also supports the offline use of thousands, or millions of apps on devices that drop in and out of internet connectivity, and can sync when connected but still completely usable when disconnected.

That's some cool shit. Simple Fast Elastic. And Reliable. And Mobile. That's why Couchbase.

by Damien Katz at January 11, 2012 08:17 PM

January 06, 2012

Damien Katz

The Future of CouchDB

What's the future of CouchDB? It's Couchbase.

Huh? So what about Apache CouchDB? Well, that's a great project. I founded it, coded the earliest versions almost completely myself, I've spent a huge amount of blood, sweat and tears on it. I'm very proud of it and the impact it's had. And now I, and the Couchbase team, are mostly moving on. It's not that we think CouchDB isn't awesome. It's that we are creating the successor to it: Couchbase Server. A product and project with similar capabilities and goals, but more faster, more scalable, more customer and developer focused. And definitely not part of Apache.

With Apache CouchDB, much of the focus has been around creating a consensus based, developer community that helps govern and move the project forward. Apache has done, and is doing a good job of that. But for us, it's no longer enough. CouchDB was something I created because I thought an easy to use, peer based, replicating document store was something the world would find useful. And it proved a lot of the ideas were possible and useful and it's been successful beyond my wildest ambitions. But if I had it all to do again, I'd do many things different.

If it sounds like I'm saying Apache was a mistake, I'm not. Apache was a big part in the success of CouchDB, without it CouchDB would not have enjoyed the early success it did. But in my opinion it's reached a point where the consensus based approach has limited the competitiveness of the project. It's not personal, it's business.

And now, as it turns out, I have a chance to do it all again, without the pain of starting from scratch. Building on the previous Apache CouchDB and Membase projects, throwing out what didn't work, and strengthening what does, and advancing great technologies to make something that is developer friendly, high performance, designed for mission critical deployment and mobile integration, and can move faster and more responsively to users and customers needs than a community based project.

Apache CouchDB, as project and community, is in fine shape. And many of us at Couchbase are still contributing back to it. But the future, the one I'm pushing forward on, is Couchbase Server.

And what is my part in building Couchbase? Right now I'm focusing on getting Couchbase 2.0 ready for serious production use. I'm once again an engineer and coder, back in the trenches, designing and writing code, reviewing code and designs, helping other engineers and solving tough problems. And I'm dead serious about making it the easiest, fastest and most reliable NoSQL database. Easy for developers to use, easy to deploy, reliable on single machines or large clusters, and fast as hell. We are building something you can put your mission critical, customer facing business data on, and not feel like you're running a dirty hack.

Soon, to work more closely with the team (and get rid of my nasty Oakland commute), I'll be relocating my family to the Mountain View area. Shit just got real!

And I'm really excited about the work we've got in the pipeline. We are moving more and more of the core database in C/C++, while still using many of the concurrency and reliability design principles we've proven with the Erlang codebase. And Erlang is still going to be part of the product as well, particularly with cluster management, but most of the performance sensitive portions will be moving to over C code. Erlang is still a great language, but when you need top performance and low level control, C is hard to beat.

Anyway, there so much to talk about, to much for one blog post. One of my New Years resolutions is to blog more, and I've got a ton of interesting things to talk about. The trials of tribulations of building a startup and an engineering culture. What's wrong (and right) with Erlang. Bringing forth UnQL. TouchDB for Mobile. And yes, we'll still interoperate with Apache CouchDB and Memcached. But the future is Couchbase.

Ride with me.

Edit

As J. Chris Anderson notes in the comments, Couchbase is completely open source and Apache licensed:

Everything Couchbase does is open source, we have 2 github pages that are very active:

https://github.com/couchbaselabs

https://github.com/couchbase

Probably the most fun place to jump into development is the code review: http://review.couchbase.org/

Let me clarify, if you like Apache CouchDB, stick with it. I'm working on something I think you'll like a lot better. If not, well, there's still Apache CouchDB.

by Damien Katz at January 06, 2012 01:19 AM

December 27, 2011

ejabberd@jabber.ru

ejabberd 2.1.10, 3.0.0-alpha-5 and exmpp 0.9.9

ejabberd 2.1.10, 3.0.0-alpha-5 and exmpp 0.9.9 have been released, after several months of development. They contain a few bugfixes.

ejabberd 2.1.10

These are the major bugfixes:

• Erlang/OTP compatibility
  • Support Erlang/OTP R15B regexp and drivers (EJAB-1521)
  • Fix modules update in R14B04 and higher
  • Fix modules update of stripped beams (EJAB-1520)
• XMPP Core

read more

by badlop at December 27, 2011 07:38 PM

October 03, 2011

ejabberd@jabber.ru

ejabberd 2.1.9, 3.0.0-alpha-4 and exmpp 0.9.8

ejabberd 2.1.9, ejabberd 3.0.0-alpha-4, and exmpp 0.9.8 have been released, after several months of development. They contain a lot of bugfixes, improvements and some new features.

ejabberd 2.1.9

This release includes a lot of bugfixes and improvements. This is just a short list of them:

• New SASL SCRAM-SHA-1 authentication mechanism (EJAB-1196)
• New option: resource_conflict (EJAB-650)

read more

by badlop at October 03, 2011 04:04 PM

October 01, 2011

Erlang Announce List

Erlang announce mailing list :: erlang.org mailing list memberships reminder

Author: Anonymous
Subject: erlang.org mailing list memberships reminder
Posted: Sat Oct 01, 2011 3:02 am (GMT 0)
Topic Replies: 0

This is a reminder, sent out once a month, about your erlang.org
mailing list memberships. It includes your subscription info and how
to use it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes. For more info, send a message to the '-request' address of
the list (for example, mailman-request@erlang.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@erlang.org. Thanks!

Passwords for trapexit.erlang-announce@erlang-solutions.com:

List Password // URL
---- --------
erlang-announce@erlang.org nU78uRu6
http://erlang.org/mailman/options/erlang-announce/trapexit.erlang-announce%40erlang-solutions.com
Post received from mailinglist

October 01, 2011 03:15 AM

September 27, 2011

Damien Katz

Become a Distributed Database Expert (or just look like one)

At Couchbase we are looking for experienced hackers to help us build the fastest, most reliable distributed database on the planet. You don't need to a be expert already, but you should be ready to learn the ins and outs of distribute database systems, including:

• Distributed Systems
• Systems Resource Management: io (disk, network), cpu, memory usage
• Maximizing Throughput and Minimizing Latency
• Functional programming
• Systems Reliability
• Network Programming
• Profiling, Benchmarking and Optimization
• Cluster and Network Topology
• Replication and Logical Sync
• Distributed Data modeling
• Embedded and Mobile software

More info here: http://www.couchbase.com/company/jobs Or you can send your resume and qualifications to me here: damien@couchbase.com

by Damien Katz at September 27, 2011 10:08 PM

September 24, 2011

Damien Katz

Re: Data sync

>On Sep 23, 2011, at 1:40 AM, XXXX XXXXX wrote:
>
>Hi Damien,
>
>Greeting from XXXXX XXXXXX;
>
>Im running a small company with history in the mobile enterprise space
>
>We are just about to get some seed funding to build sqllite sync
>technology for mobile devices;
>
>I came across CouchBase extremely cool;
>
>We are planning to offer some of same features;
>
>Offline access
>Smart sync
>Bandwidth optimisation
>
>It would be good to get any advice or pointers you might have in
>terms of building sync technology for mobile
>
>All the best,
>
>XXXX XXXXX,

Hello! I would say that mobile sync is a deceptively hard problem to get all the nice properties you want. I suggest you look at how Couchbase replication works and try to duplicate it, and ideally, try to interoperate with it.

Some of the properties you probably want:

Incremental replication - The ability to stop and restart replication and not lose all your progress. Vital in a mobile environment where connections are slow and flaky.

Concurrency -You want to be able to use the local and the remote the databases while it's getting sync'd/replicated, no global locking. So the app is usable at all times and syncing in the background.

Conflict management - You need plan for how you'll deal with and manage edit conflicts.

Partial replication - Having replicas that only hold a interesting subset of other replicas. Important when sharing a large data set, but mobile clients only need a portion of it.

Ad hoc Topology - Couchbase supports ad hoc topology, any machine can sync with any other machine without prior knowledge. This is much more flexible than a single centralized sync point or fixed topology. Though many deployments will only need a single sync point, often new ones will need to be added.

Schema upgrade - Couchbase is schemaless, so it's easy to add new field/properties without breaking things. If using a schema, it's difficult to upgrade remote clients when they have new data in older schemas, etc.

Security - the ability to refuse updates if the come from unauthorized sources.

Anyway, Couchbase and CouchDB has worked out these problems and is successful in production on millions of machines. It's not the only way to build a sync scheme, but it's one of the most successful.

-Damien

by Damien Katz at September 24, 2011 06:26 PM

September 01, 2011

Erlang Announce List

Erlang announce mailing list :: erlang.org mailing list memberships reminder

Author: Anonymous
Subject: erlang.org mailing list memberships reminder
Posted: Thu Sep 01, 2011 3:02 am (GMT 0)
Topic Replies: 0

This is a reminder, sent out once a month, about your erlang.org
mailing list memberships. It includes your subscription info and how
to use it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes. For more info, send a message to the '-request' address of
the list (for example, mailman-request@erlang.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@erlang.org. Thanks!

Passwords for trapexit.erlang-announce@erlang-solutions.com:

List Password // URL
---- --------
erlang-announce@erlang.org nU78uRu6
http://erlang.org/mailman/options/erlang-announce/trapexit.erlang-announce%40erlang-solutions.com
Post received from mailinglist

September 01, 2011 03:15 AM

August 29, 2011

Erlware

We have moved to blog.erlware.org

We have moved!! You can find us here at http://blog.erlware.org We have packed up and moved our blog onto a subdomain of our main site. This blog will probably stay up for a good long time but we will not be writing anything new here but we will also not be moving the posts from this blog to the other. Cheers, Erlware Team

by Martin J. Logan (noreply@blogger.com) at August 29, 2011 10:25 AM

July 07, 2011

Damien Katz

Break's Over. Big Mover. Couchbase changing the Game.

There is some seriously cool stuff coming up at CouchConf on July 29. One the things I'm most excited about is Richard Hipp, creator of SQLite, will join me on stage to talk about our current joint project. Can't tell you what it is right now, but if you feel the Earth shift a little that day, you'll know why...and be sure to watch this space on July 29 to learn the details!

by Damien Katz at July 07, 2011 10:52 PM

June 21, 2011

Damien Katz

Couchbase Training Summer Special

We are doing a special training deal this summer--$395 for two days of training!

The next one is in Portland in just a couple days on June 27 and 28! If you're in Portland for OSBridge, or you are in the area, you should definitely sign up.

http://www.couchbase.com/couchdb-training/portland-june-2011

Also, if you're in NYC this summer and want to learn about Membase Server, we'll be doing a class on July 11 and 12th.

http://www.couchbase.com/membase-training/nyc-july-2011

We only have a limited number of seats so it's important to sign up ASAP.

by Damien Katz at June 21, 2011 07:59 PM

June 16, 2011

Damien Katz

CouchConf Early Bird Special Ends Tomorrow

Sign up by Friday, June 16, for the early bird rate. CouchConf is July 29 in San Francisco.

CouchConf is the only conference dedicated to all things Couch. This one-day event is for any developer who wants to take a deeper dive into Couchbase technology, learn where it's headed and build really cool stuff.

Sign up now!

by Damien Katz at June 16, 2011 03:57 PM

June 03, 2011

ejabberd@jabber.ru

ejabberd 2.1.8 - Fix PubSub

The ejabberd 2.1.7 released yesterday contains a bug that breaks PubSub.

If you use ejabberd 2.1.7 and PubSub, you can find the patch and the fixed mod_pubsub.beam in the page EJAB-1457.

Updated binary installers will be available next monday in http://www.process-one.net/en/ejabberd/downloads

by badlop at June 03, 2011 11:39 AM

June 01, 2011

ejabberd@jabber.ru

ejabberd 2.1.7, 3.0.0-alpha-3 and exmpp 0.9.7 -- security release

Update: ejabberd 2.1.8 was released with a PubSub fix.

ejabberd 2.1.7, and ejabberd 3.0.0-alpha-3, and exmpp 0.9.7 have been released, after a few months of development. They contain a lot of bugfixes, improvements and some new features.

If you have ejabberd running in a public server, please update it immediately: those releases contain a security fix that disables entity expansion completely to prevent billion laughs DoS attack (CVE-2011-1753).

ejabberd 2.1.7

read more

by badlop at June 01, 2011 05:05 PM

May 19, 2011

Damien Katz

I'm in Boston next week for a Couchbase Meetup

Get yo couch on! Sign up here: http://www.meetup.com/Boston-CouchDB/events/17374461/

damien@couchbase.com

by Damien Katz at May 19, 2011 07:03 PM

March 21, 2011

Damien Katz

Couchbase SF Training Was Awesome

I had a blast teaching the first Couchbase CouchDB Training with training pro Alan McKean last week. 2 intensive days of hands on teaching and talking about Apache CouchDB to enthusiastic and excited people. It was actually a learning experience for me too, there's a lot in CouchDB I haven't had a chance to use yet :)

It's not too late to sign up for the remaining 3 cities on the Couchbase Training World Tour: Austin, London and Berlin.

by Damien Katz at March 21, 2011 10:49 PM

March 16, 2011

ejabberd@jabber.ru

ejabberd 3.0.0-alpha-2 - more alpha testing

This second alpha includes many bugfixes over alpha-1.

The complete list of related tickets can be found on:
http://redir.process-one.net/ejabberd-3.0.0-alpha2

Please note that the database schema used in this preliminary release is not yet definitive, and it will probably change in the next alpha and beta releases.

When compiling the source code, it is necessary to install exmpp

read more

by badlop at March 16, 2011 12:12 PM

March 07, 2011

Damien Katz

Is Node.js an application server?

An insightful comment on Reddit about Node.js:

And the idea that you fully understand your own code is a bit suspect, too. My code's all nice and fast until somebody passes me in a POST request with a million keys, or decides to upload a 10GB file where I was expecting a 5KB file and I run a hash algorithm over it, or I accidentally use way more memory than I expected and push the system into swap, or any number of other things like that. My life would be a lot easier if my code never did anything I didn't expect.

I keep wondering where Node fits in a production environment and who writes the code that powers it.

by Damien Katz at March 07, 2011 03:00 AM

March 03, 2011

Damien Katz

So You Wanna Learn About CouchDB?

CouchDB World Tour Coming! Along with Alan McKean, I and other Couchbase staff will be doing 5 training sessions in 5 different cities starting in March. I'll be teaching the San Francisco one :) We've developed some incredible material that I'm really excited to present. So go ahead and sign up, and bring a friend!

Sign up now

Claire was so inspired she wrote a song about it:

http://vimeo.com/20499717

by Damien Katz at March 03, 2011 01:43 AM

February 24, 2011

ProTest news

Erlang Factory London 2011 - Talk Submission Open

The Erlang Factory London 2011 is returning once again and will be held on 6th – 10th June 2011 and we have opened the call for talk submissions.

Do you have what it takes to lead a conference session or tutorial? Have you made an interesting innovation, open source application or product with Erlang/OTP? Have you used Erlang in a real-world project and want to present a case study? Or have you developed a cool tool and want to give a hands-on tutorial? Tell us about it.

We welcome submissions from developers, system designers, testers, community leaders, inventors, CTOs, evangelists, students, researchers and entrepreneurs alike. Participants at the Erlang Factory want to hear about how Erlang/OTP is used real-world scenarios, talks about tricks, tools and applications which increase productivity or enable developers to write better code.

The deadline for talk submissions is the 11th April 2011 and you can submit yours here.

You can follow @erlangfactory on twitter for the latest news.

by ProTest-Project Web at February 24, 2011 12:00 AM

February 09, 2011

Damien Katz

CouchOne + Membase = Couchbase

I've got some news I'm extremely excited to finally announce: a merger between CouchOne and Membase!

A little background, I met James Phillips, the co-founder of Membase, for the first time in December. I'd heard a little about Membase up to that point, but I was most impressed with some of their high profile users. For example, Membase is a key part of Zynga, where giving millions of users a fast, low latency experience is critical.

Membase has been targeting large scale mission critical apps, being able to scale out quickly and support millions of users, and getting impressive traction. They'd been going after a very specific pain point, a completely different part of the market than what we were targeting. They've focused on performance and scalability and exploiting all the power and memory available on modern servers. Simple, Fast, Elastic.

At CouchOne we've been focusing on very different problems: mobile, sync and offline use cases. We make it easy to build applications that travel with you, allowing you access to your important data no matter the network conditions. Slow and unreliable connectivity means many businesses can't rely on the cloud for mission critical apps, all their data is gone when their network is down. But with Couch powered apps on your phone, tablet, putting data directly on the machines at the edge of the network, you have your apps and data with you at all times and safely backed up to the cloud.

Couchbase!

What James had is the vision to see the great fit between the two companies. While independently we were both doing very well, we both have a lot of growing to do yet. And amazingly, the direction Membase needed to grow, we were already doing very well. And in the direction we needed to grow, Membase was already doing very well. Not only were the part of the stack we were focusing different and complementary, but the way we built out our teams was different and complementary. I'm not sure we could have planned it any better, and we didn't plan it at all!

And so I'm thrilled to announce Couchbase, a merging of both our companies and our technology!

Technologically, we'll be joining the products together to create a high volume, low latency, elastic clustered Couchbase server system. A Couch that's Simple, Fast, Elastic with all the reliability and power of CouchDB. We'll also continue to support the Membase API, for both backwards compatibility and it's performance advantages over HTTP. We will be the only solution out there that can scale to Zynga sized workloads and down to phones and tablets and everything in between, supporting millions of users and keeping everything in sync.

For existing CouchDB users, we will fully support CouchDB's HTTP API with all its associated benefits: seamless integration with other HTTP based infrastructure, a universally supported, human-readable protocol and direct-browser access just to name a few.

Together as Couchbase, we'll have the fastest, most scalable (both scale up and scale down) NoSQL solution. We will become the standard storage for mobile devices, and the standard server technology for syncing them all together. Our unified solution will dramatically simplify your technology stack and maintenance for building fast responsive apps that scale to millions of users, and also scaling down to phones so people can work and play even when not connected to the network.

My role at Couchbase will be CTO, overseeing the technical direction of the company. Dustin Sallings will be the chief architect. Bob Weiderhold will be CEO and co-founder James Phillips will continue to be product-oriented maniac :) CouchOne co-founders Chris Anderson and Jan Lehnardt will take roles to lead our mobile efforts and to work with our developers and community.

What's in it for you?

It's all upside! In the short-term we'll be able to provide a much better developer and support experience for both for CouchOne and Membase technologies, and move the development speed ahead much faster. The long term benefits are that CouchDB users will acquire the high performance, high scale easy-fast-elastic capabilities of Membase, while Membase users will acquire CouchDB's indexing features (map/reduce views, lucene, R-Tree GeoCouch), replication, reliability, and an easy path to mobile.

This is hot stuff! 2011 is the year of Couchbase!

by Damien Katz at February 09, 2011 06:09 PM

January 18, 2011

ProTest news

Erlang Solutions launches a course in Test Driven Development with Erlang

by ProTest-Project Web at January 18, 2011 12:00 AM

January 13, 2011

ProTest news

Programme Announced for the Erlang Factory SF Bay Area 2011

by ProTest-Project Web at January 13, 2011 12:00 AM

December 14, 2010

ejabberd@jabber.ru

ejabberd 2.1.6 - CAPTCHA support, Shared Rosters LDAP

ejabberd 2.1.6 has been released, after four months of development. It contains a lot of bugfixes, improvements and some new features.

This is a small list of changes:

• BOSH: Fix rare loop, support vhosts, allow module restart
• Config: Default configuration allows registrations only from localhost
• Config: Support to change loglevel per module at runtime
• Erlang/OTP: Fix compatibility from R10B-9 to R14B01
• ODBC: Compatibility with PostgreSQL 9.0
• Privacy lists: Fix to allow block by group and subscription again

read more

by badlop at December 14, 2010 11:56 AM

November 19, 2010

Erlang Announce List

Erlang announce mailing list :: Erlang/OTP now at Github

Author: Anonymous
Subject: Erlang/OTP now at Github
Posted: Wed Nov 25, 2009 2:14 pm (GMT 0)
Topic Replies: 0

The official git repository for Erlang/OTP can now be found at Github:

http://github.com/erlang/otp

Build instructions can be found at:

http://wiki.github.com/erlang/otp

We plan to add more wiki pages with additional information in the
near future.

--
Björn Gustavsson, Erlang/OTP, Ericsson AB

________________________________________________________________
erlang-announce mailing list. See http://www.erlang.org/faq.html
erlang-announce (at) erlang.org

Post received from mailinglist

November 19, 2010 10:16 AM

Erlang announce mailing list :: Erlang/OTP R13B03 has been released

Author: Anonymous
Subject: Erlang/OTP R13B03 has been released
Posted: Wed Nov 25, 2009 1:56 pm (GMT 0)
Topic Replies: 0

Bug fix release : otp_src_R13B03
Build date : 2009-11-23

This is R13B03, the third maintenance release for the R13B major release.

You can find the README file for the release at

http://www.erlang.org/download/otp_src_R13B03.readme

The source distribution and binary distribution for Windows can be
downloaded from

http://www.erlang.org/download/otp_src_R13B03.tar.gz
http://www.erlang.org/download/otp_win32_R13B03.exe

The distribution can also be downloaded using the BitTorrent
protocol. Use the following torrent files to download the source
distribution and binary distribution for Windows:

http://www.erlang.org/download/otp_src_R13B03.tar.gz.torrent
http://www.erlang.org/download/otp_win32_R13B03.exe.torrent

Note: To unpack the TAR archive you need a GNU TAR compatible program.

For installation instructions please read the README file that is part
of the distribution.

The on-line documentation can be found at: http://www.erlang.org/doc/
You can also download the complete HTML documentation or the Unix manual files

http://www.erlang.org/download/otp_doc_html_R13B03.tar.gz
http://www.erlang.org/download/otp_doc_man_R13B03.tar.gz

We also want to thank those that sent us patches, suggestions and bug
reports,

The OTP Team

--
Björn Gustavsson, Erlang/OTP, Ericsson AB

________________________________________________________________
erlang-announce mailing list. See http://www.erlang.org/faq.html
erlang-announce (at) erlang.org

Post received from mailinglist

November 19, 2010 10:16 AM

November 16, 2010

ejabberd@jabber.ru

Happy 8th birthday, ejabberd!

ejabberd gets 8 years old. But no party yet, Yozhik is bugfixing 2.1.6 and testing 3.0.0-alpha-2.

The source and more photographs of hedgehogs pets.

read more

by badlop at November 16, 2010 04:34 PM

November 12, 2010

Damien Katz

CouchOne on wsj.com

CouchOne gets some coverage on the Wall Street Journal site. They even posted our awesome CouchDB music video. Nice :)

WSJ Venture Capital Dispatch: Music Video For Database Start-Up? That's How CouchOne Rolls

by Damien Katz at November 12, 2010 11:49 PM

October 13, 2010

Erlware

Console Applications in Erlang

This tutorial is brought to you by ErlangCamp 2010 - Chicago, October 23 and 24 - already at 95% capacity! It's gonna be totally sweet.Erlang is probably not the first language you'd think of for building console applications. Here's a typical "Hello World" application in Erlang:-module(hello).-export([hello/0]).hello() -> io:format("Hello World!~n").After compiling the module, you'd run it as

by Garrett Smith (noreply@blogger.com) at October 13, 2010 09:29 AM

Damien Katz

Madison Williams is available in the Bay Area

My younger brother Madison is looking to relocate to the SF Bay Area.

He's a young guy with a lot of talent and lots of real world experience designing and creating web apps. Most recently he's created Arik, cool blog software built on PHP and CouchDB.

He'll be in Bay area (my house to be exact!) Oct. 23-27 for some job interviews. Contact him before he's all booked up!

Resume: http://www.madisonwilliams.net/resume.php
Blog: http://www.madisonwilliams.net/

by Damien Katz at October 13, 2010 05:48 AM

September 24, 2010

ProTest news

Speakers and Talks Announced for the Erlang User Conference 2010

The program has been finalised for the Erlang User Conference.

With talks from Motorola, Google, Basho, Gemini Mobile and many more, this year's conference is packed full of exciting talks, with great speakers such as Simon Thompson, Kenneth Lundin, Tino Breddin and Joseph Wayne Norton.

Registration for the Sixteenth International Erlang User Conference and Erlang University courses is open. Register now for the Early Bird Discount and pay only SEK 1,000 including VAT! DON’T MISS OUT as last year's conference sold out.

The Sixteenth International Erlang User Conference will take place in Stockholm, on the 16th November 2010.

In addition to the conference itself, there will be the Erlang University - three-day Erlang training courses from 17th to 19th November. There will also be a day of Erlang Tutorials on the 15th.

Registering for one of the University courses: Erlang Express or OTP Express includes entry to the Erlang User Conference, so don't waste time and register now!

by ProTest-Project Web at September 24, 2010 12:00 AM

September 11, 2010

Damien Katz

CouchCamp was

Awesome!

GeoCouch Session With Max Ogden

More:
Selena Deckelmann - CouchCamp 2010: yay!

by Damien Katz at September 11, 2010 08:59 PM

September 08, 2010

Damien Katz

CouchDB in Wood Format

How cool! Thank you Ben!

by Damien Katz at September 08, 2010 09:37 PM

September 07, 2010

Erlware

Flymake and Erlang

Flymake is a really useful tool for programming Erlang, or for programming in general, that gives you on the fly error detection in source files. It does this by compiling your source code in the background and showing the results in file you are editing. It doesn't actually know anything about languages or how to compile, it is built in a very abstract way such that it can be used for any

by Eric Merritt (noreply@blogger.com) at September 07, 2010 09:14 AM

September 01, 2010

Damien Katz

What's New in CouchDB 1.0 Security 'n Stuff

Today, I get a little help from Rebecca. She's writing a CouchApp, an application that is served right out of CouchDB and that lives in the browser. It has no middle tier application server in Ruby or Java. The application and display logic is written in JavaScript, the user interface is HTML & CSS, the backend is CouchDB and uses Ajax to shove JSON back and forth.

What's new in CouchDB 1.0 -- Part 4: Security 'n Stuff: Users, Authentication, Authorisation and Permissions

by Damien Katz at September 01, 2010 12:36 AM

August 27, 2010

Damien Katz

Why Large Hadron Collider Scientists are Using CouchDB

A nice article on ReadWriteWeb: http://www.readwriteweb.com/enterprise/2010/08/lhc-couchdb.php

And the case study: http://www.couch.io/case-study-cern

by Damien Katz at August 27, 2010 02:51 AM

August 25, 2010

ProTest news

Erlang User Conference Registration Open with a Very-Early Bird Rate!

Registration for the Sixteenth International Erlang User Conference and Erlang University courses are now open. The first 100 people to register will receive a Very-Early Bird Discount and pay only SEK 750 including VAT! DON’T MISS OUT as last year's conference sold out.

The Sixteenth International Erlang User Conference will take place in Stockholm, on the 16th November 2010.

In addition to the conference itself, there will be the Erlang University - three-day Erlang training courses from 17th to 19th November. There will also be a day of Erlang Tutorials on the 15th.

Registering for one of the University courses: Erlang Express or OTP Express includes entry to the Erlang User Conference, so don't waste time and register now!

Speakers and talks will be announced shortly.

by ProTest-Project Web at August 25, 2010 12:00 AM

August 21, 2010

Damien Katz

The Little Comedian

Gwen: Knock knock.

Me: Who's there?

Gwen: Knock knock.

Me: Who's there?

Gwen: Knock knock.

Me: Who's there?

Gwen: Banana!

Me: Banana who?

Gwen: Orange you glad I didn't say orange again?

Us: BWAHAHAHA!

by Damien Katz at August 21, 2010 01:53 AM

August 14, 2010

Erlware

ErlangCamp - Erlang and OTP Workshop in Chicago Oct 23 and 24

ErlangCamp is here! You may have seen the announcement on the erlang.org already. ErlangCamp is a two day hands on workshop for those interested in learning how to go from novices or experienced levels of programming Erlang to being able to confidently write production grade Erlang/OTP services. ErlangCamp is an opportunity to learn from those who have done a ton with OTP and Erlang and put many

by Martin J. Logan (noreply@blogger.com) at August 14, 2010 01:18 PM

August 13, 2010

Damien Katz

WARNING: CouchDB 1.0.0 Data Loss bug

Update August 13, 2010. A data recovery tool now available: http://wiki.couchone.com/page/repair-tool

if you are running CouchDB 1.0.0 with the default delayed commit setting, you are subject to serious data loss on restart. See this page for instructions how to force all outstanding commits and configure your server at runtime to run in the safer full commit mode: http://couchdb.apache.org/notice/1.0.1.html

The page also includes details of the bug and a postmortem.

0.11.1 and earlier are unaffected. Servers with delayed commits turned off are unaffected. 1.0.1 will be coming shortly that fixes the problem in all configurations.

DO NOT COMPACT THE DATABASE! Compaction throws away any lost updates permanently.

Data recovery is coming. The CouchDB core contributors are working on a utility to reliably recover lost updates, so no data is lost as long the database file is not compacted.

by Damien Katz at August 13, 2010 06:42 PM

August 06, 2010

ejabberd@jabber.ru

ejabberd 3.0.0-alpha-1 - for alpha-testing only

This first alpha includes three major changes compared to ejabberd 2.1.5: exmpp library is used, gen_storage for a database abstraction layer, and Massive Hosting which isn't yet usable.

Many tables have changed both in Mnesia and MySQL/PgSQL/ODBC. Fortunately, now ejabberd is able to create tables, update the tables and reformat their content in Mnesia and also in external databases. Or at least it should do.

read more

by badlop at August 06, 2010 10:01 PM

Damien Katz

CouchDB Diplom Thesis

It's whooping 163 pages containing all the nitty-gritty-researchy details on why CouchDB is the number one choice for writing distributed applications in both the small and large scale.

Diplom Thesis: Realisation of a Distributed Application Using the Document-Oriented Database CouchDB by Lena Herrmann

by Damien Katz at August 06, 2010 12:30 AM

August 04, 2010

Damien Katz

We are hiring open source contributors!

We are hiring front end and back end engineers, documentation writer, trainer, release engineer and managers. Must have an open source background. See our jobs page for more info:

http://couch.io/jobs

by Damien Katz at August 04, 2010 11:36 PM

August 01, 2010

Damien Katz

Getting Your Open Source Project to 1.0

The project I founded, Apache CouchDB, recently hit 1.0. I'm very proud :)

Awesome 1.0 cupcakes from Sauce Labs.

It's been a long time, but we finally produced a release that's complete, performs well and is rock solid.

Already CouchDB is on over 10 million machines. It's used by big respected websites (like the BBC) and groundbreaking organizations (Mozilla and Canonical). We run on most *nix, OS X, Windows, and even Android phones. Have dozens of frameworks and client libraries available. There are 2 books available for sale right now. There is a venture capital backed startup, Cloudant, that offers CouchDB hosting and scales to huge datasets. And I'm CEO of another venture backed ($2 million invested) 12 person start-up, Couchio.

So how did I get here? It took a lot of time and effort (almost 5 years!), and the help of a lot of people. Here are some tips of what it took to get CouchDB to 1.0.

Why?

Successful open source projects need a reason for being. You need to decide why you are creating a project and what problems it solves. Whether it's one or many reasons, you need to figure out what they are and explain them.

Perhaps you are making something new, that hasn't existed. Why hasn't it existed it before? No had the idea? No one had the will to carry it through? Or maybe you are making something that's already in existence, like an HTTP server. What are your reasons? Simpler, faster, more features, different license?

If you are just doing it as a learning exercise, that's fine. But don't expect to attract a community until you can explain why it's useful beyond you own personal goals.

With CouchDB, my reasons were:
1. A schemaless document database with views, bi-directional replication and conflict detection to enable disconnected operation would be really useful.
2. I wanted to understand more about creating distributed systems and database internals.

No one cares about reason #2 except for me. But the first reason is compelling.

Make sure you can tell people why your project exists and what it's good for. And put the reasons on your project site where people can find them.

Code Comes First

Don't start a project unless you have a deep commitment to being a strong coder.

Now I'm not saying you must be a strong coder to participate in a project. Not at all. I'm saying that you must be strong coder to lead one. Maybe you'll get lucky and somehow attract a some really good coders to your project. But most really good coders go to projects with already solid codebases, or start their own.

Also, you don't have to be a strong coder when you start out, but you should know the basics and have a strong desire to learn and get better. Don't expect to attract anyone to your project until you have a substantial amount of working code that isn't a big ball of spaghetti.

With CouchDB, I always emphasized the quality of the high-level design and code implementation. We cannot under any circumstances lose or corrupt your committed data, or get things into an inconsistent state. Reliability and durability are absolutely imperative. Any design or implementation that doesn't meet these goals doesn't make it into the project.

Some projects might not have an emphasis on the reliability, but on absolute performance. That's a fine choice to make, but make sure your users know what they are trading off. And then actually deliver on the performance.

As the project moves along, you will need to ensure the code quality (reliability, performance, resource, usage, etc) is improving over time. If you aren't a good coder, you won't be able to do this.

Know What You Aren't

Almost as important as knowing what your project is trying to accomplish, is know what it isn't trying to accomplish.

When your project starts to get traction, but before it's done, you'll get a lot of people who want the project to work more like things they've used in the past. New users might think your goals and abilities are cool, but they'd trade it all for just a little more. They'll want everything your project does, plus a pony.

The problem is feature and scope creep. Even if you are successfully keeping the project on track, the community may get slowed down dealing with people trying to make it something it's not. Stating clearly what your project isn't trying to do or be helps make it much easier to explain what you can't implement or change.

Now, you can't define everything your project isn't. (It's not a video game. It's not accounting software. It's not a banana. It's not a rainbow. etc.). But you can find the things it's related to, overlaps with, or might be confused with, and explicitly say it's not those things.

With CouchDB, because we are a database, people often asked us to add features that were in traditional RDBMS's, but didn't fit well with the CouchDB data model. Not being intimately familiar with CouchDB's model and how it all fits together, they don't realize that what they're asking for simply doesn't work. But because we explicitly stated on the project site we aren't a relational database and aren't trying to replace relational databases, it made it much easier to explain why those features weren't a good fit for what CouchDB is trying to accomplish.

So if you don't clearly define what your project isn't, often people will try to make it into those things. This can damage the community, as moving forward is slower and people feel like they aren't being listened to. Be explicit what you aren't, and it makes it much easier to focus on what you actually are.

Don't Do Everything (Well)

So you are superstar coder, your code is clear and concise and high quality, you write clear complete documentation, your create all the tests, and you fix every bug. You are awesome!

Thing is, you might be awesome, but until you actually get a community behind the project, the project will be limited in an absolute sense by what a single person can produce. And if you are doing everything, that's not a whole lot. Trying to do everything well means you'll probably never actually release anything.

Unfortunately, at first, you _will_ need to do everything. But just don't do everything really well. Instead, you'll have do some things crappily, and then move on. In addition to writing all the code, you'll need to: Create a project site. Explain your project. Write documentation. Do the releases. Start a bug tracker. Create a mailing list and answer questions. And you'll have to do most of these things poorly if you want to keep moving the ball forward.

You'll have to do some things poorly. But you'll need to pick a few things that you do really well and execute on those things. (The code should be one of the things you do well).

And everything you do, you'll need to make it easy for others to participate. To add patches, to update and create documentation, make bug reports and send patches. And make it clear that help is desired.

Don't get hung up on trying to make everything perfect. That just paralyzes you. But by picking a few things to do well, you will attract people to help you with the things you aren't doing well.

Community Wants to Help

Open Source is awesome in the way it attracts people who just want to help make something cool. Many people want to contribute their time, but only if they think their help will amount to something in the long run. They don't want to spend time and effort on something that doesn't yet show potential or might be abandoned if the creators lose interest.

If you have a solid codebase, then it becomes much easier to attract people to your community. If people can recognize there is at least something high quality about your project, but it's lacking in some areas, people will want to help you in those areas. But you have to have the high quality pieces in place. People don't want to be the one excellent contributor to dreck. They'd rather not have their efforts associated at all.

They do want to be a part of something great. They want to add their work and make it even better. They want to contribute to projects where the total excellence of the project reflects well on them and their efforts. They want to make the world a better place, and don't want their efforts wasted.

And people who like making the world a better place are exactly the kind of people you want to attract. You want people to have pride in their contributions, and to feel like they are really positively affecting the things they care about. Those people have lots of projects to choose where they can add their time and talents. If they feel their efforts on your project are wasted, they are gone. Make sure the people who show a strong desire to contribute aren't ignored, and feel like their efforts will eventually amount to something.

Being a part of Apache has helped CouchDB tremendously. Partially it's because Apache has helped our visibility and credibility. But it's also because we've adopted the "Apache Way", which is more focused on the community aspects of a project than on any specific contributor. Without our amazingly active community, CouchDB would be far behind where it is now.

Community Is Often Incompetent

Unfortunately, many people who will want to help you will produce contributions of poor quality. You will have deal with this "help", and do so diplomatically. The best way to point out the shortcomings with their contributions is to identify what needs improvement without denigrating their overall effort. This can be hard, and many don't want to hear why their efforts aren't up to the project's standards.

Sometimes you have to hurt peoples feelings. But it's better to be honest then to have the quality of your project brought down. If they can't handle the feedback, so be it. The good news is the people who do listen to constructive criticism and actually improve the quality of their contributions are incredibly valuable. Look for these people and nurture their involvement.

With CouchDB, we try to listen to all members of our community, but we only grant commit access to the ones who have shown high quality contributions. Our committers are our first line of defense against poor code and design.

Paul Graham Was Right

It seems to make sense to choose a mainstream language for your project. The more mainstream it is, the larger the potential community you can attract. While that's true to an extent, the quality of the community is more important than its absolute size. Much more important.

Using a mainstream language means you are also competing for contributor's time from other projects in the same language. So the pool is large, but in the end, you still have to attract quality developers from other things competing for their attention. And the competition might actually be stronger in that larger pool.

The more mainstream a language, the more likely it is that a random developer knows it because it's what they use at work. They aren't necessarily interested in being more productive, being more reliable, or whatever. They are interested in getting paid, and they choose their language not for elegance, power or performance, but for the number of job openings available.

If you pick a non-mainstream, more esoteric language, you tend to get a higher quality of developer. You tend to find people who absolutely love programming and building, and choose their languages not based on the scale of pay, but because they make the developers and projects more powerful. So while the total pool of contributors is smaller, they tend to give a higher quality of contribution. You get a much better signal to noise ratio.

As Paul Graham explained in Beating the Averages, the exotic languages tend to attract devs who love to learn and expand their toolbox. You'll attract more of the types of devs who don't mind creating new code to fill in the gaps, or diving into source to find a bug. They aren't afraid of what they don't know, they actually get excited by the chance to learn and do something new.

But if you pick enterprisey language X, you might find you are spending more of your time fixing problems and dealing with developers who just don't "get it". If you aren't careful, this can drown your project and bring the total code quality down to the point where you can't find good devs to help you anymore. With the less popular, esoteric languages, that tends to be less of a problem and you get a higher quality of contribution in general.

Use Your Brain

I can keep listing all the stuff we did, but you aren't creating the same project under the same circumstances. Pretty much everything I've said here, we've not followed at some point during the project. Often it was to the detriment of the project, but sometimes it just didn't make sense to blindly follow a rule or guideline.

You have a brain, and using it is the most important thing to remember at anytime. Projects can't follow cookie cutter rules. Even the "Apache Way", as I've discovered, means different things to different people, often at different times.

So take my advice here with a grain of salt, and use your brain to figure out what's actually important to you, your project and it's community. Good luck!

by Damien Katz at August 01, 2010 05:38 PM

July 26, 2010

Damien Katz

CouchCamp is Coming Soon!

CouchCamp, September 8-10

This is the place to be to learn and hack on Apache CouchDB. In honor of the recent 1.0 release, for a limited time it's only $500, with accommodations.

In addition to unconference style discussions, we've got some great speakers: Selena Deckelman, Stuart Langridge, Ted Leung, Josh Berkus, Dion Almaer and me :)

One thing I'm really excited to talk about is our work porting CouchDB to mobile platforms. Android, iOS, RIM, etc. We've got some very cool stuff coming :)

by Damien Katz at July 26, 2010 05:10 PM

July 08, 2010

Erlware

A Brief Overview of Concurrency.

Introduction Over the last few weeks I have had several conversations with people about concurrency, more specifically the ways in which shared information is handled in concurrent languages. I have gotten the impression that there isn't really a good understanding of whats out there in the world of concurrency. That being the case it would be a good idea to just give a quick overview of some of

by Eric Merritt (noreply@blogger.com) at July 08, 2010 04:33 PM

June 22, 2010

Damien Katz

Migrating From MySQL to CouchDB

Here is a detailed white paper from John P. Woods of Interactive Mediums, going into depth about their migration of their mobile marketing archive from MySQL to CouchDB.

http://www.couch.io/migrating-to-couchdb

by Damien Katz at June 22, 2010 06:08 PM

CouchCamp, aka BurningCouch!

.

Registration for CouchCamp is now open. CouchCamp is our conference about CouchDB, September 8th - 10th 2010 at Walker Creek Ranch, north of the Bay area.

This is the event to learn all about CouchDB and it's innards, the community, and how much beer I can drink before hurling. It's going to be fun!

by Damien Katz at June 22, 2010 05:12 PM

June 19, 2010

Erlang Eclipse IDE

[erlide] Regular update site upgraded

The regular update site at http://erlide.org has been updated to the now not so new p2 update manager format. Only the latest 0.8.3 build is available there.

Older stable releases are to be found at http://erlide.org/update_classic, if needed.

This is so that we can appear on the Eclipse marketplace, which will be integrated in Eclipse in the upcoming 3.6 version.

regards,
Vlad

by vladdu@users.sourceforge.net (Vlad Dumitrescu) at June 19, 2010 08:21 PM

June 18, 2010

Damien Katz

How Software Is Built: Apache CouchDB

Here is a detailed interview I recently did for HowSoftwareIsBuilt.com about CouchDB, document databases, cloud and replication:

http://howsoftwareisbuilt.com/2010/06/18/interview-with-damien-katz-apache-couchdb/

by Damien Katz at June 18, 2010 06:31 PM

June 17, 2010

Erlang Eclipse IDE

[erlide] Dropped support for R11

Version 0.8.1.201005250801 is the last to support R11, unless it will be required by enough users (or payed for with enough beers!) This is because R14 can no longer load R11 beam files and we don't have resources to keep two tracks alive.

Version 0.8.3.201006171129 is functionally identical except that the Erlang code is compiled with R12.

regards,
Vlad

by vladdu@users.sourceforge.net (Vlad Dumitrescu) at June 17, 2010 12:51 PM

June 16, 2010

Erlware

Build Process Integration

IntroductionThis post isn't going to be Erlang or Language oriented at all. One of my other hobbies revolves around the build process and build process tools. Over the last few years I have been spending a lot of time thinking about improving them, making the build process more transparent etc. I have a way to do that, I believe. Unfortunately, it would take the cooperation of build too

by Eric Merritt (noreply@blogger.com) at June 16, 2010 08:52 AM

May 27, 2010

Erlware

Why Not To Use Distributed Supervision

Let's take the example of distributed supervision. Let's say we have one supervisor on node A that supervises children on node B and node C. What happens if network throughput slows down on the connection from Node A to Node B? This isn't transparent to the Supervisor on Node A. What should the supervisor on Node A do in this case? It has no contact with node B, so it's unsure whether or not the

by Eric Merritt (noreply@blogger.com) at May 27, 2010 09:52 AM

April 01, 2010

Erlware

SF Erlang Factory Talks and Slides

For those of you who would like to view the presentation slides from the speakers, these are now available here: http://www.erlang-factory.com/conference/SFBay2010/talks (please click on the icon underneath the individual talk description). Erlang Solutions have posted most of the photos from the conference on Flickr: http://www.flickr.com/photos/erlang-consulting/collections/72157623733690054/

by Martin J. Logan (noreply@blogger.com) at April 01, 2010 01:03 PM

March 26, 2010

Erlware

Erlang Factory: Martin Logan, Eric Merritt, Richard Carlson: Writing a Technical Book

<!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } --> Where to start Writing a technical book is at least as hard as you think it is, porbably even more. The main prerequisite is believing you have something important and worth saying. After that the next thing to do is to choose a medium. In this case a publisher. They chose manning. The first step is writing

by Jordan Wilberding (noreply@blogger.com) at March 26, 2010 02:59 PM

Erlang Factory: Michael Truog The Cloud as an Interface

A Cloud as an Interface - http://cloudi.org/Cloudi - not for webapps or data cloud, but for processing. For managing processes and making sure they are fault tolerant.Cloudi is a flexible framework for private cloud computing. Its dynamically loud balanced and scheduled. Distributed execution of C/C++ work.Cloudi is an alternative to paying for a blackbox commercial cloud.Erlang coordinates all

by Tristan Sloughter (noreply@blogger.com) at March 26, 2010 12:35 PM

Riak Search

Riak SearchPresented by John Muellerteile from Basho.Fulltext and general indexing methods.Agenda* Intro* A search Tale* Riak search"I used to make stuff" (but now I'm a database hacker)Got sick of having to roll own indexes.Act 1: I love luceneLife is good, fast and predictable.Act 2: Cluster LuckA few shards, good performance.Act 3: SANFULots of shards. Operational nightmare. Diminishing

by Tristan Sloughter (noreply@blogger.com) at March 26, 2010 12:19 PM

Git Basics

Mastering Git BasicsGiven by @mojombo the cofounder and cto of github.Initial Config:git config --global user.name [NAME]git config --global user.email [EMAIL]git config --global color.ui trueLast one gives nice colors for diffs and such.Creating and CommittingMake a dir for your project:$ cd patch/to/repos$ mkdir hello$ cd hellogit init$ git init # converts empty directory into a git repo.

by Tristan Sloughter (noreply@blogger.com) at March 26, 2010 12:18 PM

Erlang Factory: Jack Moffit: Erlang Is Our Superpower

<!-- @page { margin: 0.79in } P { margin-bottom: 0.08in } --> Introduction to Erlang Started as a game, chess park. Play chess online. Were python guys, so wrote it in python. Decided to use XMPP for all the wonderful features it has. Started using jabbberd. Weren't happy with it. Decided to look at ejabberd, which led them to Erlang. New Product Wanted to have a

by Jordan Wilberding (noreply@blogger.com) at March 26, 2010 12:09 PM

Powered by Planet!
Last updated:
February 06, 2012 05:17 PM