SamePost is a new atomization service especially designed for the social network VKontakte. It greatly facilitates the work, saves time:
- for organizers of joint purchases (repeating records, random images, reposts will perfectly suit);
- for group administrators (deferred posting and batch creation of records);
- for just opened public, owners of several groups (create hundreds of records in a few clicks);
- for beginner, or already experienced SMM-box.
More details about what exactly it helps to do and how to read here.
Main features of the service:
- Attach random images that will always be different;
- Attaching albums from VKontakte;
- Attach video from VKontakte;
- Repost your entries in other groups and on your personal page;
- Convenient, customizable repeat of records;
- Schedule, which will save time when creating records;
- Create picture-records in batches;
- and many more interesting things in the future, try it!
You can also read about how Anna used the SamePost service to automate her work in the sphere of organizing shopping meetings.
The service is free, but with some paid functions. You can easily use the site even from your mobile phone, since we optimize it for mobile platforms.
Join us:
Website: https://samepost.ru
Vkontakte: https://vk.com/samepost
Extras: News
In this article we will focus on MongoDb. Almost everybody has heard about it, but not everybody imagines what it is. Some people know from rumors that this is something interesting and something more useful than mysql. Some cannot even say this. And some have already used it in their projects, but did not quite understand why... simply because they were told to. This article should clarify some omitted points or fill in the gaps in knowledge
We offer Comet ("Long Polling") technology, the basic idea of which is the transmission of information to browser on the initiative of the server. Comet servers implement HTTP Push Relay Protocol. The client connects to the web-server channel with a unique key (makes a usual connection and passes a unique channel key in parameters), and the server keeps the connection until the next portion of data
Initially, this problem appeared during going to the same page in another browser tab, if the script is fairly long and, in addition, the work with the session is necessary in the script. Two requests are queued and the next is proceeded only after the previous one is finished. An illustrative example of the code:
The article is dedicated to the system that we have invented for a deployment of our projects. We prefer GIT, so the deployment process is shown in the context of this VCS.
What is the crucial problem with delivering the notifications? In my opinion the features of a simple, flexible and stable notification system are: