<br><br><div class="gmail_quote">On Wed, Jun 3, 2009 at 5:51 PM, Peter A. H. Peterson <span dir="ltr"><<a href="mailto:pedro@tastytronic.net">pedro@tastytronic.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
How do we forsee this happening? I'd definitely prefer it as an update<br>
mechanism, not a "download the whole nki blob" thing. If we gzip it,<br>
it's really not going to take much bandwidth or space at all.<br>
<div class="im"><br>(...)<br>
</div><div class="im"><br>
</div>Maybe we can come up with a spec for rfk message management and people<br>
can choose where to get their updates. The message set at<br>
<a href="http://robotfindskitten.org" target="_blank">robotfindskitten.org</a> will remain the "official" packaged set of NKI,<br>
while</blockquote><div><br>An update mechanism is definitely better than fetching a whole blob each time there's an update. <br><br>
Heres some loose thoughts while the notion its still fresh in my head :)<br>
<br>Updates mean versions, so we could go along the lines of svn for example. Theres a global version
number, bumped each time any changes are made. Every time a nki is
modified its own version would be updated to reflect the global version
when the change took place. This way a client would request an update
from version x to the latest version and in response receive all nkis
witch were updated or created after version x.<br>
<br>
If there's packages then a separate list for packages should be
maintained (simple - like id, name, version) for the sake of keeping
stuff organized.<br clear="all">
<br>
So to recap a nki would contain<br>* the message <br>* package (or packages?) it belongs to <br>* a 'last modified' version number<br>* some unique id to identify it by<br>* propably some other fields like author and so on<br>
<br>However i dont really have an idea how such updates would be carried out. Maybe each time anything is modified the version gets bumped, but then we end up with lots and lots of updates that contain a single modification/addition. Or they could be grouped together to roll out a numbered 'release' when the person in charged feels hes finished with the update. But that feels like a hassle, maybe we could come up with something simpler that suits our needs.<br>
<br>Ok, this message is starting to become too long so ill leave it at that for now.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Lajcik's could be bigger but might be more "alpha". </blockquote><div><br>To be honest there hasnt been much activity, mostly i added a handful of my own nkis when i thought i had a good idea and thats it. But still its a start :)<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I am definitely open to some kind of automated NKI submission form, etc.<br>
here at <a href="http://robotfindskitten.org" target="_blank">robotfindskitten.org</a> but won't have the time to think about it<br>
for at least a few weeks.<br>
</blockquote><div><br>Im glad youre liking the idea :) Having a centralized submission/repository system would really be a blast. I can help with coding when this thing gets rolling.<br></div></div><br><br>-- <br>My digital home - <a href="http://lajcik.org/">http://lajcik.org/</a><br>