[Info-vax] OT: Record locking for web transactions
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Mon Feb 17 18:29:52 EST 2014
On 2014-02-17 23:16:44 +0000, David Froble said:
> Jan-Erik Soderholm wrote:
>>
>> The web is basicaly stateless, so you never keep locks from one access
>> to another.
>
> This is also my understanding. Basically, you're talking about a
> different environment and concepts than what we all grew up with.
> ...
> Or have an open socket connection, and if it goes down, trash the
> entire thing, sort of like with the old modems, lose carrier, and you
> lose your loged in process.
>
> But again, nobody asked me ....
If you want to maintain connections and state and not have to go Page
Mode Terminal on your application, then Javascript and Java running
client-side can allow that. As does Adobe Flash Player and some other
tools, for that matter.
For one of the general constructs here, see Ajax
<http://en.wikipedia.org/wiki/Ajax_(programming)>, as well as other
<http://en.wikipedia.org/wiki/XMLHttpRequest> related mechanisms.
For server-side using Javascript, see Node.js
<http://en.wikipedia.org/wiki/Node.js>, as well as other server-side
options; some of the proprietary and the open-source cloud stacks
(<http://owncloud.org> <http://www.openstack.org> etc) might be useful
here, too.
If Javascript or Java doesn't work for local needs, then various
alternative approaches continue to use HTTP or HTTPS for communications
— same protocol, though not as is used with traditional web browsing —
where your server might communicate with a platform-native application
running on Android or iOS or whatever your target platform.
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list