Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
On 11/30/06, Selem Delul [EMAIL PROTECTED] wrote: Nokia did it. (http://wiki.opensource.nokia.com/projects/Mobile_Web_Server ) So yeah, it is possible. They are using a gateway to translate an url to your phone's web server (and i guess they are using it to communicate with the phone which is behind the operator's proxy) On 11/30/06, Jeff Andros [EMAIL PROTECTED] wrote: It may be easier if the phone has an accessable IP address... I'm not quite sure how GPRS works, some one who knows let me know... but we could set up a embedded web server on the openmoko device itself. ICS is really simple so we could host that from the device as well. If Apache isn't small enough, even stripped down, there are several server apps that are optimised for this kind of environment What about using a repository of a version control system on the server PC (CVS or better Subversion) to keep the files and using add commit update to transfer data? This way you could easily recover any mistake you do on your data but there is need for more space. Subversion also has a binary diff algorithm to store differences for non textual files. This could easily serve as information transport mechanism and some script that do an add on creation of new data (provide connection is not needed), do a commit when there is a connection and do an update on the serve could do the trick. Just my 2c and yes I've been working _a lot_ with subversion lately :) Bye all, Alessandro ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
Here's another idea, this one less than half-baked, but I trust this community to help identify the flaws, seek the gems, and see if anything remains that is useful. My current phone is the Danger Sidekick II. One of its features that I really like is the web page that Danger provides that duplicates the data on my phone: Calendar, address book, notes files, todo list, photographs, email, and perhaps others. Modifications can made either on the web page or on the phone. There is no special sync command. Data entered on the one is available on the other almost instantly, assuming data network connectivity. Syncronization happens automatically and constantly. I recognize that there are security flaws with this. Remember Hilton's video? This is how it was stolen. Here's how I use it: I jot down notes all day long on my phone. At home, I visit the web page and simply cut and paste my notes into emails, documents, even programs. The nice thing about this is that I always have access to the data on my phone, and I don't have to worry about any special sync cables or cradles or software (all my home computers run Linux, so I can't use most phone desktop programs). I never have to worry about leaving my cradle at home, and needing the data at work. I'm a big fan of CVS, and I often CVS important files from my phone. And of course I can quickly check my calendar or address book from any browser, anywhere. Now I have many issues with Danger's implementation of this feature, but I really like the idea. I'm not that familiar with other smart phones, but I've never seen, or heard about, anything like this with the others. Of course our implementation will be open, so I can make it do exactly what I want. For example, provide an API, so that I can write a cron job that every so often will download all data off the phone and CVS it. Remember, the phone doesn't have to be in a cradle for this to occur. Heck, the phone could even be powered off, and my cron job would get the last version that made it to the server. I think that Danger provides the servers for this; in our implementation we would probably have to each provide our own, which means we'd have to write the server side code as well. I suppose this is all done with PHP, Java, and other languages that I don't know about (I'm more of a kernel/device driver/embedded/hardware guy). We could implement as much or as little security as we wish (SSL, encryption, etc.) What do you think? Michael ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
This isn't really half baked at all, all you need is a webserver on the device small enough to run 1-2 clients and https... It's even better than the danger since everything runs on your phone... you have control of security, and we could even make a monitor app that displays when someone's accessing your webserver --Jeff On 11/29/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Here's another idea, this one less than half-baked, but I trust this community to help identify the flaws, seek the gems, and see if anything remains that is useful. My current phone is the Danger Sidekick II. One of its features that I really like is the web page that Danger provides that duplicates the data on my phone: Calendar, address book, notes files, todo list, photographs, email, and perhaps others. Modifications can made either on the web page or on the phone. There is no special sync command. Data entered on the one is available on the other almost instantly, assuming data network connectivity. Syncronization happens automatically and constantly. I recognize that there are security flaws with this. Remember Hilton's video? This is how it was stolen. Here's how I use it: I jot down notes all day long on my phone. At home, I visit the web page and simply cut and paste my notes into emails, documents, even programs. The nice thing about this is that I always have access to the data on my phone, and I don't have to worry about any special sync cables or cradles or software (all my home computers run Linux, so I can't use most phone desktop programs). I never have to worry about leaving my cradle at home, and needing the data at work. I'm a big fan of CVS, and I often CVS important files from my phone. And of course I can quickly check my calendar or address book from any browser, anywhere. Now I have many issues with Danger's implementation of this feature, but I really like the idea. I'm not that familiar with other smart phones, but I've never seen, or heard about, anything like this with the others. Of course our implementation will be open, so I can make it do exactly what I want. For example, provide an API, so that I can write a cron job that every so often will download all data off the phone and CVS it. Remember, the phone doesn't have to be in a cradle for this to occur. Heck, the phone could even be powered off, and my cron job would get the last version that made it to the server. I think that Danger provides the servers for this; in our implementation we would probably have to each provide our own, which means we'd have to write the server side code as well. I suppose this is all done with PHP, Java, and other languages that I don't know about (I'm more of a kernel/device driver/embedded/hardware guy). We could implement as much or as little security as we wish (SSL, encryption, etc.) What do you think? Michael ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
On Wed, 2006-11-29 at 13:42 -0800, [EMAIL PROTECTED] wrote: Here's another idea, this one less than half-baked, but I trust this community to help identify the flaws, seek the gems, and see if anything remains that is useful. This will be the first application I will develop. I love it - That is an itch I want to scratch. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
On Wed, 29 Nov 2006, Redvers Davies wrote: On Wed, 2006-11-29 at 13:42 -0800, [EMAIL PROTECTED] wrote: Here's another idea, this one less than half-baked, but I trust this community to help identify the flaws, seek the gems, and see if anything remains that is useful. This will be the first application I will develop. I love it - That is an itch I want to scratch. I'm honored, and thrilled. It's one application that would be a struggle for me to write, and one I would sorely miss. Let me know how I can help! Michael ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
I love this idea and I would like to suggest a method of handeling a portions of it... Use web services... Web methods or whatever you call it. If you build an api for uploading sets of data they could be implelented in almost any lauguage and used natively like normal objects. Perl, php, python, java, c# can all do that and it means the backend does not have to be rewritten every time someone wants to use it in a language. Also, you could then provide a bundle of code for the server backend that handles the web service requests which anyone could run and point their own phone at their server. Authentication included. /shrug just an idea. --Tim ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
On Wed, 29 Nov 2006, Tim Newsom wrote: I love this idea and I would like to suggest a method of handeling a portions of it... Use web services... Web methods or whatever you call it. If you build an api for uploading sets of data they could be implelented in almost any lauguage and used natively like normal objects. Perl, php, python, java, c# can all do that and it means the backend does not have to be rewritten every time someone wants to use it in a language. Also, you could then provide a bundle of code for the server backend that handles the web service requests which anyone could run and point their own phone at their server. Authentication included. /shrug just an idea. --Tim I guess what you're saying is that my original idea requires a certain infrastructure: an API which the Neo can use to communicate with a server, and code running on the server which can understand and respond to the Neo's requests. Perhaps the server too can initiate the conversation. A library and API is required on the server side too. So now you have a general purpose library upon which a server application can be written that can exchange data with the Neo, including authentication, encryption, etc. Given this library, any application can be written on the server. My original wish is just an example of one, in which case the UI is a web page. But much more than this can be done, limited only by our imagination. Am I understanding you correctly? Michael ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
Use web services... Web methods or whatever you call it. If you build an api for uploading sets of data they could be implelented in almost any lauguage and used natively like normal objects. Perl, php, python, java, c# can all do that and it means the backend does not have to be rewritten every time someone wants to use it in a language. Also, you could then provide a bundle of code for the server backend that handles the web service requests which anyone could run and point their own phone at their server. It may be easier if the phone has an accessable IP address... I'm not quite sure how GPRS works, some one who knows let me know... but we could set up a embedded web server on the openmoko device itself. ICS is really simple so we could host that from the device as well. If Apache isn't small enough, even stripped down, there are several server apps that are optimised for this kind of environment ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
Yeah. But more specifically I am defining the type of api as web services or web methods (they are the same thing usually). Basically, the web method is a standard used to define the remote method calls, their required parameters and types of acceptable data from within a program. Any program which can use web methods could use the same backend services. Its language neutral. Its also transport neutral. You can define encrypted channels to be used as the communication mechanism and regardless of which channel is used, the api does not get altered. Web services isolate the data transport mechanism from the application. I could draw up the architecture but its pretty simple. App -- calles web method from remote server and passes in data. The data gets stored.. The reverse is also true if you want a fetch process to occur. Web services also define types of activity as synchronus and asynchronus... Synchronus would be like a normal web request where you specify the url, sometimes with parameters and get a page back immediately. Asynchronus is more like subscribe/notify. You tell the service you want something and when its available or changed, based on the implementation, the response is sent back to you. Its all bi-directional since any request can send some kind of data and properly implemented, there is no reason you could not share data between multiple neo's using the same interface. I hope that's a little clearer... Maybe other with web services background can help me explain the concept and maybe correct me if I stated anything in error. --Tim ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
Right.. For peer to peer or requests directly to the phone that's true. There is no reason we could not build a community shared server to be the intermedary between the phones however... Something that doesn't store the data longer than necessary for another phone to retreive the information. Then you could pass encryped information securely, even if the server itself was not secure by encrypting it in advance of sending it to the share. Obviously, accessable ip addresses on the phone would be preferred but might not be possible. --Tim ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
Nokia did it. (http://wiki.opensource.nokia.com/projects/Mobile_Web_Server) So yeah, it is possible. They are using a gateway to translate an url to your phone's web server (and i guess they are using it to communicate with the phone which is behind the operator's proxy) On 11/30/06, Jeff Andros [EMAIL PROTECTED] wrote: It may be easier if the phone has an accessable IP address... I'm not quite sure how GPRS works, some one who knows let me know... but we could set up a embedded web server on the openmoko device itself. ICS is really simple so we could host that from the device as well. If Apache isn't small enough, even stripped down, there are several server apps that are optimised for this kind of environment ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Please think about incrementel sync Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
Salve Jeff,*! When it will be only adresses, todo, memo - syncML is build to do this. But please via a secure network - Siemens offer this unencrypted. *help*help*help*help* On Wed, 29 Nov 2006, Jeff Andros wrote: for uploading sets of data they could be implelented in almost any lauguage and used natively like normal objects. Perl, php, python, java, c# can all do that and it means the backend does not have to be rewritten every time someone wants to use it in a language. Also, you could then provide a bundle of code for the server backend that handles the web service requests which anyone could run and point their own phone at their server. It may be easier if the phone has an accessable IP address... I'm not quite sure how GPRS works, some one who knows let me know... It has an IP and this makes me worry that the area of IPs for GPRS are known and someone would send you anwanted packets just for fun to encrease your mobil bill. If I had a chance I would take an option that the operater will protect my mobil will a firewall and only two connections to my two server would be allowed. (I have big doubts that this would work with beeing abroad with a GPRS roaming partner some day). So everybody should track his GPRS costs automaticaly. but we could set up a embedded web server on the openmoko device itself. This will be an option, but will encrease the GPRS traffic = costs. For having everyfile *save* on the server http://www.drbd.org/ But to lower the traffic costs the transmission of data should be reduces as much as possible and wait until it is realy needed, or a cheap connection (USB, data call...) would allow to sync. Just let the server ask if since he last asked the Neo some configuration has changed and transmit it only incremental. A little bit the same with normal files. How do you think that a file will make a diff with itself (the modification) before it is modificated and save the modicated version + all diffs since last replication with the server. The server could ask the Neo for seperate direction pathes (tree parts) for informations about changes. A list of the files that have been changed inbetween (on inode level?) will be transmitted to the server. When you open such a file on the server, the server will ask for the diff. Transmission bzip2 compressed and via VPN Without thougths like that you will have an incredible GPRS traffic = costs. ICS is really simple so we could host that from the device as well. If Apache isn't small enough, even stripped down, there are several server apps that are optimised for this kind of environment A webserver will change the layout of the neo... I like to propose the alternative Frontend, to have an OpenMoko/NSLU2 at home with syncronisation and to use NX to forward the X to your webbrowser... Greetings, rob ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Fwd: Please think about incrementel sync Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
snip
Without thougths like that you will have an incredible GPRS traffic =
costs.
ICS is really simple so
we could host that from the device as well. If Apache isn't small
enough,
even stripped down, there are several server apps that are optimised for
this kind of environment
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.
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:
{user to phone} request update/commit cycle from phone to repository
{user on desktop} update local copy of phone filesystem
{user on desktop} make appropriate changes to files
{user on desktop} commit to repository
{user to phone} request update from repository
where you are not on your phone, and are making commands from a browser
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
--Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Please think about incrementel sync Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
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.
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...
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
OR
You would have to have the repository local and commit the changes locally
but that doesn't help with the storage part. The only way to sync up would
be through the dock.
My understanding of svn is that it transmits the entire file and the svn
server does the diff and only stores the differences between the files at
the repository. I could be wrong about that though.
If you don't keep a repository locally then one way or another you will have
to obtain a copy of the old version in order to just sync changes somehow..
Its an interesting thought.. does anyone know for sure if SVN sends back
only the changes and how it does that if it doesn't fetch the previous
version for comparison?
--Tim
btw.. I tend to over explain things so if I don't go far enough please ask
me (I am trying to cut back) ;-)
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. ;-)
On 11/29/06, Jeff Andros [EMAIL PROTECTED] wrote:
snip
Without thougths like that you will have an incredible GPRS traffic =
costs.
ICS is really simple so
we could host that from the device as well. If Apache isn't small
enough,
even stripped down, there are several server apps that are optimised
for
this kind of environment
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.
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:
{user to phone} request update/commit cycle from phone to repository
{user on desktop} update local copy of phone filesystem
{user on desktop} make appropriate changes to files
{user on desktop} commit to repository
{user to phone} request update from repository
where you are not on your phone, and are making commands from a browser
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
--Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
--
-- Tim
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Please think about incrementel sync Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
On 11/29/06, Tim Newsom [EMAIL PROTECTED] wrote:
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.
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 here:
www.asu.edu/clubs/paddle http://www.asu.edu/clubs/paddle 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
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...
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
Now that you mention it, I'm not really that sure either... but I think
you're right.
snip
--Tim
btw.. I tend to over explain things so if I don't go far enough please ask
me (I am trying to cut back) ;-)
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. ;-)
amen, brother, amen
On 11/29/06, Jeff Andros [EMAIL PROTECTED] wrote:
snip
Without thougths like that you will have an incredible GPRS traffic =
costs.
ICS is really simple so
we could host that from the device as well. If Apache isn't small
enough,
even stripped down, there are several server apps that are optimised
for
this kind of environment
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.
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:
{user to phone} request update/commit cycle from phone to repository
{user on desktop} update local copy of phone filesystem
{user on desktop} make appropriate changes to files
{user on desktop} commit to repository
{user to phone} request update from repository
where you are not on your phone, and are making commands from a browser
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
--Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
--
-- Tim
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
--
--Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
Re: Please think about incrementel sync Re: Another idea for an application for the Neo: Instant sync to web page duplicating info on phone
So here is a document talking about some of the things we have mentioned...
From the link to nokia...
http://research.nokia.com/tr/NRC-TR-2006-005.pdf
Interesting, they have thought of quite a bit of this already.
--Tim.
On 11/29/06, Jeff Andros [EMAIL PROTECTED] wrote:
On 11/29/06, Tim Newsom [EMAIL PROTECTED] wrote:
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.
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 here:
www.asu.edu/clubs/paddle http://www.asu.edu/clubs/paddle 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
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...
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
Now that you mention it, I'm not really that sure either... but I think
you're right.
snip
--Tim
btw.. I tend to over explain things so if I don't go far enough please
ask me (I am trying to cut back) ;-)
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. ;-)
amen, brother, amen
On 11/29/06, Jeff Andros [EMAIL PROTECTED] wrote:
snip
Without thougths like that you will have an incredible GPRS traffic
=
costs.
ICS is really simple so
we could host that from the device as well. If Apache isn't small
enough,
even stripped down, there are several server apps that are
optimised for
this kind of environment
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.
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:
{user to phone} request update/commit cycle from phone to repository
{user on desktop} update local copy of phone filesystem
{user on desktop} make appropriate changes to files
{user on desktop} commit to repository
{user to phone} request update from repository
where you are not on your phone, and are making commands from a
browser
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
--Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
--
-- Tim
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
--
--Jeff
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
--
-- Tim
___
OpenMoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/cgi-bin/mailman/listinfo/community
