Tag Archives: promise

Announcing Dycapo 0.0.2

As promised, Dycapo 0.0.2 is out. Dycapo will be an open client (mobile)/server system that will improve travel experiences of users in a city. The system will let people to define a destination on their mobile phone. DyCaPo will suggest and arrange trips by either using the Public Transport Service or Carpooling volunteers. That is,

On the automation of API writing and XML-RPC serving for Python Django

While searching for solutions on adopting Django for the server side of our Dynamic Car Pooling system, I found two very interesting projects: WAPI – a framework which abstracts the details involved in publishing an API and translates class methods to API methods, serializing the objects returned when possible. WAPI handles authentication, too, and other

Wiki set up, first meeting

Both the Wiki and the blog has been set up. Tomorrow I’m going to have the first official meeting at FBK to discuss my first results. I’ve just finished the grid containing a short description that each paper proposed as a solution (or suggest) for the areas: System Suggestions Interface Design Algorithms Coordination Trustiness Safety/Reputation

Heap vs. Stack in C++

After the study of pointers versus references, the second natural question that comes in head of a ex Java developer turning to C++ is: “What are the difference between static and dynamic memory allocation in C++?” which can be translated as: “When should I use the stack and when do I have to use the

Introduction to HTTP mind-map

As I promised about 4 hours ago, here is my introduction to Hyper Text Transfer Protocol in form of a mind map. It is to be intended as a really short introduction to this protocol. Like the previous one about computer networks, the mindmap summarizes materials copyrighted by Tanenbaum and also material taken from Wikipedia.

BD-incollo 0.1 is out!

As I promised, BD-incollo 0.1 is finished and the source code is available in the project page under the GPL 3 license. Every MUST requirement has been done and just two MAY requirements could not be developed in just 6 days. But They will surely be in the next releases. Sourcecode is well commented using