iOS chat application design, sending/relaying the message over to the end user
I have a design question. Let us say you were tasked with building a chat application, specifically for iOS (iOS Chat Application). For simplicity let us say you can only chat with one person at a time (no group chat functionality).
Form cancellation. Where should any data rollback occur?
You have a form that has an object injected into it. The user interacts with the form and updates the injected object via the UI. If the user then ‘Cancels’ the form, whose responsibility is it to undo those changes?
Form cancellation. Where should any data rollback occur?
You have a form that has an object injected into it. The user interacts with the form and updates the injected object via the UI. If the user then ‘Cancels’ the form, whose responsibility is it to undo those changes?
Form cancellation. Where should any data rollback occur?
You have a form that has an object injected into it. The user interacts with the form and updates the injected object via the UI. If the user then ‘Cancels’ the form, whose responsibility is it to undo those changes?
Form cancellation. Where should any data rollback occur?
You have a form that has an object injected into it. The user interacts with the form and updates the injected object via the UI. If the user then ‘Cancels’ the form, whose responsibility is it to undo those changes?
Form cancellation. Where should any data rollback occur?
You have a form that has an object injected into it. The user interacts with the form and updates the injected object via the UI. If the user then ‘Cancels’ the form, whose responsibility is it to undo those changes?
What is best software design in creating methods?
I had created a extension method which extended the string type in C#.
What is best software design in creating methods?
I had created a extension method which extended the string type in C#.
How to enrich a simple two endpoint SOAP application to become enterprise level?
Imagine you have some exchange of data between two endpoints (webservices or let’s call URL).
Data can travel in any way (Xml, Json, GET, POST) it doesn’t matter.
How to enrich a simple two endpoint SOAP application to become enterprise level?
Imagine you have some exchange of data between two endpoints (webservices or let’s call URL).
Data can travel in any way (Xml, Json, GET, POST) it doesn’t matter.