| The importance of the API [message #561625] |
Mon, 10 March 2008 13:41 |
|
[Mik Kersten said]
It would help to have a short but concrete overview of what it would be
like to use the plug-in, i.e. some kind of user centric overview.
[Harm Sluiman said]
I think it will be key to make API of the artifacts you flow on the
wire between the client and server. Plus if you can keep that protocol
truly restful you will be building something for the future. The
reference model will also be critical since to get adoption you need to
be able to reference out to anything, but also be easily referenced.
Persistent references are never as easy as they sound, as you probably
know ;-)
<...>
So my net is that you need to publish API in the artifact space even
more than for plugins, and declaring API is serious stuff so don't do
it fast, but do it well. (easy for me to say ;-)) It would be good if
your proposal highlighted some of your intentions in this space.
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Tool
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
Powered by
FUDForum. Page generated in 0.01462 seconds
Search
Help
Register
Login
Home
