11–20 of 23 posts
Also, re the spark:
"No need to ever plug the Core into your computer" vs. "Power it over USB"
Edit: scratch that, https://www.spark.io/# has details of a "battery shield" with a LiPo - an idea of the battery life when running the OP's sensor application would be nice though?
What does this have to do with the "cloud?" Does it really mean "Internet?" The cloud is about scalable resources that can be elastically leased for short or long periods of time. That's different than the Internet, which is a means of communication...
Sadly, I'm not just being ironic.
Earlier quoted context omitted.
Thanks, so the answer is no, as long as that open source version is vaporware. The reason I asked is that once they get purchased by, say, Google or Facebook, their cloud services will probably get either shut down, or severely constrained. I'm not interested in sinking resources into a platform based on question marks.
I think you missed this part: > The Core lets you do your own socket programming over TCP and UDP. There's nothing stopping you from writing your own TCP/UDP listener server and having the Spark write to a port on that.
What does this have to do with the "cloud?" Does it really mean "Internet?" The cloud is about scalable resources that can be elastically leased for short or long periods of time. That's different than the Internet, which is a means of communication...
I recently was told that a product would be hosted on a local cloud.
What they meant was an NFS share.
What does this have to do with the "cloud?" Does it really mean "Internet?" The cloud is about scalable resources that can be elastically leased for short or long periods of time. That's different than the Internet, which is a means of communication...
So I take it you haven't talked to a marketing person in the last few years, eh? I recently was told that a product would be hosted on a local cloud. What they meant was an NFS share.
What does this have to do with the "cloud?" Does it really mean "Internet?" The cloud is about scalable resources that can be elastically leased for short or long periods of time. That's different than the Internet, which is a means of communication...
Earlier quoted context omitted.
From the homepage ( https://www.spark.io/ ): What if I don't want to connect through the Cloud? That's okay! The Cloud is there to make the Core easier to work with, but if you'd rather do it yourself, that's no problem. The Core lets you do your own socket programming over TCP and UDP. If you want the simplicity of the Cloud but you want it on your own server, we'll be releasing an open source version of the Cloud d…
Thanks, so the answer is no, as long as that open source version is vaporware. The reason I asked is that once they get purchased by, say, Google or Facebook, their cloud services will probably get either shut down, or severely constrained. I'm not interested in sinking resources into a platform based on question marks.
We will definitely be releasing this, we consider it a promise we made to our Kickstarter backers.
I'm looking for a wifi ingress monitor (ideally it would take a picture rather than be a simple sensor) - any suggestions. Also, re the spark: "No need to ever plug the Core into your computer" vs. "Power it over USB" Edit: scratch that, https://www.spark.io/# has details of a "battery shield" with a LiPo - an idea of the battery life when running the OP's sensor application would be nice though?
What does this have to do with the "cloud?" Does it really mean "Internet?" The cloud is about scalable resources that can be elastically leased for short or long periods of time. That's different than the Internet, which is a means of communication...
The cloud is the part of the network you don't have to care about. It started out meaning the Internet. You would draw a local network diagram, then a little cloud, then the remote network. You didn't care about who owned all the links in between, where they were, how many there were etc. People have been thinking about moving things "into the cloud" well before it became a buzzword. Moving storage into the cloud was…
* On-demand self service
* Broad network access
* Resource pooling
* Rapid elasticity
* Measured service
[1] http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145...
Earlier quoted context omitted.
The cloud is the part of the network you don't have to care about. It started out meaning the Internet. You would draw a local network diagram, then a little cloud, then the remote network. You didn't care about who owned all the links in between, where they were, how many there were etc. People have been thinking about moving things "into the cloud" well before it became a buzzword. Moving storage into the cloud was…
From The NIST Definition of Cloud Computing [1], there are five essential characteristics of cloud computing: * On-demand self service * Broad network access * Resource pooling * Rapid elasticity * Measured service If EC2/AWS doesn't meet that definition, what does? [1] http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145...