Google: android thermostatat.
Et cetera
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
Lew..I apologize whole heartedly for whatever it is I might have said to
upset you so much. I retract all my statements and hope we can get past
this and be friends. Perhaps I was too assertive in my initial claim that
today's phones could be decent servers. I didn't have the time to look up
the
Well... in fact there are apps out there that run small web-servers on your
phone, like Samsung's Kies app that allows browsing your phone's contacts
and media files from your PC's browser. It works on a LAN and I was very
intrigued by that concept so I prototyped a primitive Android web server
Well, of course, this is possible, you can simply just do the normal
Java socket stuff. The problem comes with the details of actually
using it and interfacing to it. Besides the problem of not really
having an easily addressable IP, it's just not clear what's being
asked here.
This idea
You can definitely create a TCP server on Android.
The code would look like this:
ServerSocket serverSocket = null;
boolean listening = true;
try {
serverSocket = new ServerSocket(1101);
} catch (IOException e) {
System.err.println(Could not listen on port: 1101.);
System.exit(-1);
}
while
Yes, but doing that (as I said) lends itself to an everlasting
service: you certainly can't run that code on the UI thread (it will
simply barf with an exception), and so the sensible place to put it is
in a service.. There might be times when this is acceptable, but you
should think about it
While I agree that running a web server of any sort on the android
phone/tablet is pretty pointless compared to todays entry level cheap
hardware.. most of these devices are more powerful and capable than my
development machine was 6..maybe 7 or so years ago, and we wrote cod while
running a
bob wrote:
You can definitely create a TCP server on Android.
The code would look like this:
ServerSocket serverSocket = null;
Not really necessary to initialize to null.
boolean listening = true;
try {
serverSocket = new ServerSocket(1101);
} catch (IOException e) {
On Wednesday, January 9, 2013 4:04:55 PM UTC-8, andjarnic wrote:
... I could see where rather than buying a beefy multi-cpu 2+ rack system,
you could put a bunch of these in place as servers to handle a few dozen or
so requests and with almost no heat and enough power and memory to handle
Lew wrote:
andjarnic wrote:
... I could see where rather than buying a beefy multi-cpu 2+ rack
system, you could put a bunch of these in place as servers to handle a few
dozen or so requests and with almost no heat and enough power and memory to
handle the requests.. a farm of these
Clearly you are taking this to an extreme.. my point was..given that *most*
phone devices don't get too hot that they would need a large cooling system
to keep it cool, and the fairly decent processing power of current devices,
my point was, it would be possible, to some extent, barring a few
It's not that you can't do it because of hardware restrictions, it's
that a standard implementation would lend itself to something that
violates a key Android principle.
If you're just doing it for novelty, then by all means do it. But
that's a different story than a production app. Since this
I'm sorry if I came off confrontational to your response, I didn't
mean to sound that way at all. I don't believe I'm taking this to an
extreme: this forum is for developing apps, I wanted to give a warning
that you should consider other options if you want to develop real
apps that need this
Kris, I was referring to Lew's response. Text is of course impossible to
know someone's tone, some people may just reply with what seems like
ruffled feathers answers..but might just be making a point instead.
Regardless, I don't let responses bother me for the most part, but it
seemed as if my
On Wednesday, January 9, 2013 4:44:36 PM UTC-8, andjarnic wrote:
Clearly you are taking this to an extreme.. my point was..given that
*most* phone devices don't get too hot that they would need a large cooling
system to keep it cool,
I disagree. Most phone devices get hot enough that
andjarnic wrote:
Kris, I was referring to Lew's response. Text is of course impossible to
know someone's tone, some people may just reply with what seems like
ruffled feathers answers..but might just be making a point instead.
Regardless, I don't let responses bother me for the most part,
No, I see that now, my mistake, that was just my reading too quickly..
Kris
On Jan 9, 2013, at 9:18 PM, Kevin Duffey andjar...@gmail.com wrote:
Kris, I was referring to Lew's response. Text is of course impossible to know
someone's tone, some people may just reply with what seems like
17 matches
Mail list logo
