Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I know only webservices,webrequest&webresponse,sockets are the ways to send/receive data.
can someone one please list out the various ways to send the information from one website to other website, and their pros&cons?
Which one is best under which situation?
Well the question is a bit vague but I will go ahead and get something started:
Web services(soap, rest) - soap is secure but very verbose. rest is lightweight but lacks the security that soap offers. Though you can still encrypt using https
tcp sockets- guaranteed delivery, bigger payload than udp, cumbersome to setup for web based solutions
udp sockets- lighter payload, non guaranteed delivery, ability to broadcast to all ports listening but most routers don't like this
web request/response - pretty straightforward
But as for which one to use we really can't answer that without some context for the question. What are you trying to communicate? How many clients are we communicating to? Will this be initiated or do you need to notify?
All protocols and techniques involving HTTP based data exchange.
Another intersting way would be to share the data on network-drives. Two web-applications can exchange data over a networ-drive from their back-end coding that does not involve HTTP at all.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 months ago.
Improve this question
How can I use a broker of MQTT like mosquitto, for example, without internet?
I've downloaded mosquitto, but I really don't know how to use it in my code.
I'm programming in python, so an answer in python is better for me to understand and use in my project.
We can't really answer your question without knowing what you intend to actually do with MQTT.
What I will say is the following:
A MQTT broker doesn't require "The Internet". They will (normally) require a TCP/IP network, but this can be as simple as just a TCP/IP stack on a single machine.
The broker runs on it's own, you do not (again usually) embed the broker into your application, it is used so multiple applications can pass messages to each other.
For working with any MQTT broker in Python there is the Paho Python library. It's documentation includes examples to get you started.
I suggest you start the broker and then write a couple of test Python applications (one to subscribe to a topic and one to publish to that topic) to get a feel for how things work and if you get stuck you can ask a new question about a specific problem (explaining what you tried, what you expected it to do and how it didn't work).
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
In theory, I'm looking to integrate email into a CRM I'm building. I'd like for each contact with an email address to have those sent and received emails fetched when viewing that contact with a connected IMAP account.
Would one store these emails in the database or would it be faster/more efficient to fetch these emails on the fly? (when the contact page is accessed via a GET request).
Would one store these emails in the database or would it be faster/more efficient to fetch these emails on the fly?
Have you measured the performance to find out? Don't prematurely optimize, actually identify bottlenecks. Set up some tests (large-scale, repeatable... don't just test one email one time) to retrieve emails from the CRM system vs. retrieving them from the database. See if there's a significant difference. Include that information in your decision-making process.
Additionally, there are other things to consider when making this decision. Namely:
Will these emails be modified in the scope of a transaction? Databases are good at participating in a transaction scope for a unit of work in your code, third-party services and APIs not so much. You might want to put them in the database if they're needed as part of such a scope. (Though given the description, that's unlikely.)
Duplicating data between multiple systems (multiple "sources of truth") and keeping it synchronized is hard. It introduces a lot of unexpected complexity into a system. You may see a performance gain, but is it worth it? Maybe some application-level caching will yield just as much of a gain without duplicating the data and introducing another dependency into the mix?
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
So I know this is a pretty simple question, but I've looked through all of my iOS textbook and can't seem to find out how people do this. I just want to store and edit an array on the internet. That is, let's say all of the data for my application is stored in an NSMutableArray. Ignoring the complications that occur with people editing the array at the same time, how would I allow multiple people to go into my app and then through that app access and edit the NSMutableArray for others to see?
There are a ton of options here, some of which were listed by #Zaph. The most common scenario to share data between a ton of random users is to setup your own server to run an API that you app will be able to communicate with. This is commonly referred to as the "Backend". The solutions here are vast, written in many different languages and sometimes even provided by third parties services. My advice is to pickup a simple, easy to learn server-side setup like Ruby-on-Rails, then deploy test app on Heroku as they provide free accounts to play with.
In addition to the options #coneybeare provided some others include DropBox, Parse and Azure.
Dropbox requires each user so setup an account.
Parse and Azure have rather easy APIs but you will be paying past the free tier.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have a news application that i am in the process of building, and of course news updates a lot, so I have to constantly update my stories, so I need a backend of some sort that will let me update my stories over the air without updating the actual app.
I found Parse.com and they have some awesome stuff, but with the way my app is built I don't think I can use them.
I will have to update UIImageviews, UItextviews, and the names of Buttons. With Parse I can only seem to find help regarding the PFQueryTableViewController, which I could use this, but that requires completely recoding and some redesigning of my app to fit into that.
So unless there's another way, I guess I will suck it up and get to work.
So is there a simpler way to do this, or maybe a better service that works more towards what I'm describing?
What you are asking basically is how to do network communication. It sounds like to me you can do what you want with just Parse. You just store the images and text and then call the information from the parse backend when you are loading. From there you can update the UITextViews, button names, and UIImageViews however you want dynamically (using the .text, setTitle, and .image properties and methods respectively). You could also use Amazon S3 for image storage... but the API is less well documented for that.
This is probably your best bet, unless you really want to delve in more deeply and learn how to use NSURLConnection or AFNetworking to communicate with a back-end that you build on a django, ruby, etc. server that you host yourself on a server.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I was reading through this article:
http://aws.typepad.com/aws/2008/12/running-everything-on-aws-soocialcom.html
And I was wondering if this was good or bad. I am a fan of AWS myself, but I what to hear what the crowd thinks...
There is everything perfect in the Elastic World besides reliability. Obviously, the reliability and quality of service is dependent on the service provider and if the service provider is down you don't have anything to fallback on. I am a big proponent of AWS, but with the last two outages, I am now designing fallback on local data center servers in case of outages.
One of the main design decisions when designing a solution in AWS is to expect services to fail and implement mechanism to recover and if you need HA, then implement redundancy. Don't assume all the services to be reliable (Unless otherwise stated that they implement redundancy internally). Most of these problems are solved if you are using managed services such as Lambda, API Gateway, S3, Dynamodb & etc but if you are using services like EC2, then you have to design for HA, for example for EC2 using auto scaling and load balancing.
If you are interested to learn more refer AWS Well-Architecture Framework Whitepaper.