So here is a document talking about some of the things we have mentioned... From the link to nokia...<br><br><a href="http://research.nokia.com/tr/NRC-TR-2006-005.pdf">http://research.nokia.com/tr/NRC-TR-2006-005.pdf</a><br>
<br>Interesting, they have thought of quite a bit of this already.<br><br>--Tim.<br><br><div><span class="gmail_quote">On 11/29/06, <b class="gmail_sendername">Jeff Andros</b> <<a href="mailto:whitedrought@gmail.com">whitedrought@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br><div><span class="q"><span class="gmail_quote">On 11/29/06, <b class="gmail_sendername">
Tim Newsom</b> <<a href="mailto:cephdon@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">cephdon@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Web services are XML data transfer. The problem with xml is that it is wordy for data (size) but good for parsing. What I mean by that is that its not the most efficient way to transfer data ( ok thats obvious) but its a defined format and easy to parse just about anywhere.. just slow.
</blockquote></span><div><br>ah, but XML has a lot of good tools to offload the pretty portions onto other servers... and we can pull a Google and use one-letter tag names to cut down on space. to see what I mean check out
<a href="http://www.asu.edu/clubs/paddle" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
here: www.asu.edu/clubs/paddle</a> all the stuff that makes the site pretty is in the xsl-t page... I'm pretty sure we can cut down on the bloat by setting up our schema for minimum size<br></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If you are keeping a copy of the current versions locally then diffing and sending only the diffs would be easy... but to my knowledge svn only keeps the diffs between versions at the repository. Someone who knowns please correct me. If I understand what you are saying and based on my knowledge...
<br>You either keep an old version for diffing purposes and replace it with the current version when you do the commit. All changes happen to the original not the "old copy"</blockquote></span><div> Now that you mention it, I'm not really that sure either... but I think you're right.
<br></div><snip><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">--Tim<br><br>btw.. I tend to over explain things so if I don't go far enough please ask me (I am trying to cut back) ;-)
<br>Also, feel free to correct me if I state something wrong.. I like to be correct in my understanding and if I don't have all the necessary information I would like to know what I am missing out on. ;-)</blockquote></span>
<div>
<br>amen, brother, amen <br></div><div><span class="e" id="q_10f36c3236fd0846_7"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div>
<span><span class="gmail_quote">
On 11/29/06, <b class="gmail_sendername">Jeff Andros</b> <<a href="mailto:whitedrought@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">whitedrought@gmail.com</a>> wrote:</span></span>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><span>
<span class="gmail_quote"><br></span><snip><div><span><span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Without thougths like that you will have an incredible GPRS traffic =
<br>
costs.<br><br>> ICS is really simple so<br>> we could host that from the device as well. If Apache isn't small enough,<br>> even stripped down, there are several server apps that are optimised for<br>> this kind of environment
</blockquote></span></span><div><br>I don't do a lot of data on my phone at the moment mostly I use bluetooth for this kind of thing, so I hadn't thought about costs... the other thing we could try is an XML transfer of just the data, offloading the formatting onto another server... the cool thing about this is we could run both directly from the phone or from an intermediary depending on preferences and the particular situation.
<br><br>When you use an intermediary server, that will handle the heavy lifting on building the page and you could have a nice ajax-y interface, direct from the phone you could remotely store an XSL-T stylesheet to give you the frontend. this minimizes the data that needs to go back and forth. sending files back and forth I'd rather use something else, but in a pinch we could use an svn client which does send only the file diffs back and forth, plus storing the whole machine's drive on subversion gives us a nice backup in case someone throws you into the pool with your phone in your pocket (it's all fun and games until someone loses thier {email | phonebook | files | blackmail photos of drunk friends}) you could also use this like so:
<br><br>{user to phone} request update/commit cycle from phone to repository<br>{user on desktop} update local copy of phone filesystem<br>{user on desktop} make appropriate changes to files<br>{user on desktop} commit to repository
<br>{user to phone} request update from repository<br></div><br>where you are not on your phone, and are making commands from a browser<br><br><br>Apache/whichever servers we're running handles the encryption, and now you can get to the current version of your system through websvn from anywhere
<br></div><span><span><br>--Jeff
</span><br clear="all">
</span><br></span></div><span>_______________________________________________<br>OpenMoko community mailing list<br><a href="mailto:community@lists.openmoko.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
community@lists.openmoko.org
</a><br><a href="http://lists.openmoko.org/cgi-bin/mailman/listinfo/community" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.openmoko.org/cgi-bin/mailman/listinfo/community</a><br><br>
<br></span></blockquote></div><br><br clear="all"><br>-- <br><span>-- Tim
</span><br>_______________________________________________<br>OpenMoko community mailing list<br><a href="mailto:community@lists.openmoko.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">community@lists.openmoko.org
</a><br><a href="http://lists.openmoko.org/cgi-bin/mailman/listinfo/community" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.openmoko.org/cgi-bin/mailman/listinfo/community</a><br><br>
<br></blockquote></span></div></div><br><br clear="all"><br>-- <br><span class="sg">--Jeff
</span><br>_______________________________________________<br>OpenMoko community mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:community@lists.openmoko.org">community@lists.openmoko.org
</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://lists.openmoko.org/cgi-bin/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/cgi-bin/mailman/listinfo/community</a><br><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>-- Tim