<span class="gmail_quote"><br></span><snip><div><span class="q"><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><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 class="sg"><br>--Jeff
</span><br clear="all">