Splatforms and Third-party Developers

Posted on September 20, 2010
Filed Under Splatforms | 6 Comments | Share this post via splatforms.com

Early on we realized that the potential for what we were trying to accomplish was so broad and so varied that if we tried to do it all ourselves, we would surely fail, or at a minimum, severely limit the possibilities. Our solution to that problem was to make every effort to set things up in a way that would not make us the bottleneck or choke point at any stage of the development process. We wanted to make sure that if someone felt the need to get *form data from here, or to post *form data over there, that they could do that with minimal restrictions.

Our intent was to create a framework through which data could be channeled from any number of sources to any number of destinations. To do that, there would have to be source-specific and destination-specific components available to make that happen. Given the open-ended nature of the potential destinations for *forms data, we knew from start that there would be no way that we could personally create them all. More importantly, we knew that there was no way that we could even conceive of them all. The only way that this was going to grow into something that truly embodied that vision was to turn the keys over to anyone who had an idea for a destination-specific connector of their own design.

We call those destination-specific connectors Tasks, and we have set up a special section of the site devoted exclusively to Task Developers. Anyone who wants to can request that we set them up as a Task Developer and we’ll do it. One day, we’ll have an automated sign-up page for such a request just like we have an automated registration page for new users, but for now, just tell us you want your account set up as a developer and we’ll set you up as a developer.

We don’t have a whole lot of documentation on the Task development process just yet, but there are lots of examples out there and lots of folks willing to help out those who are interested in giving it a shot. We would encourage anyone who wants to send *form data to a specific destination that does not see an existing Task available to go ahead and try to create one. Even if you don’t feel as if you have the technical skills necessary to set up a Task on your own, if you have an idea, let us know and we’ll see if we can find someone who does. If we can provide a means to connect the people with the needs and the ideas with the people who can make it happen, then we can get out of the way and let you help each other out.

Ultimately, our goal is refine the central processing engine that facilitates the efficient transfer of data from its original source to its ultimate destination. If we can provide a solid “center” to which anyone can attach connectors to the outer “ends”, then we will have the foundation that both users and developers can leverage to meet any number of requirements. While it is true that we are creating both Tasks and Loaders of our own, it is our hope that these become samples for others just as much, if not more so, as they are products in of themselves.

Comments

6 Responses to “Splatforms and Third-party Developers”

  1. Anatomy of a Splatforms Task : Splatforms on December 2nd, 2010 12:39 pm

    […] and the evaluation criteria for each step. Because we have opened up the Task creation process to Third-party developers, virtually anyone can create a Task of their own choosing and add it to […]

  2. Auto submit to over 100 sites for free : Splatforms on December 7th, 2010 6:58 am

    […] keep piling on as time permits. And since we’ve opened up the Task development process to third-party developers, anyone else who wants to pile on is always welcome to join the party as […]

  3. Splatforms, Velocimacros, and Spintax : Splatforms on February 2nd, 2011 6:50 am

    […] don’t worry about all that VTL stuff above … that’s just there for those little Task Developers that make all of that magic happen in the background. If you’re just a regular user with no […]

  4. More Fun with Velocimacros : Splatforms on May 23rd, 2011 12:26 pm

    […] as Velocimacros. The Splatforms Task specification provides a section in the Task definition where Task Developers can include any number of Velocimacros needed during the Task processing. To get an idea of the […]

  5. Another New Version of the *forms Local Agent Released : Splatforms on June 1st, 2011 6:56 am

    […] a minor, but crippling bug in the user authentication mechanism that would only occur if the Task Developer used Velocity variables in a URL that also relied on HTTP Basic […]

  6. When Your *form Task Fails : Splatforms on July 28th, 2011 12:39 pm

    […] The good news here is this is a yet another situation that can be resolved, but unless you are the Task Developer, it’s not going to be resolved by you. You are dependent on the developer to know about, […]