Here I provide a tiny mindmap summarizing the basic concepts of UDDI.
I’m using it for studying Advanced Internet Technologies.
As sources, I used OASIS official specification and tutorialspoint.
Here I provide a tiny mindmap summarizing the basic concepts of WSDL.
I’m using it for studying Advanced Internet Technologies.
As sources, I used W3C official specification and w3schools.
Here I provide a tiny mindmap summarizing the basic concepts of SOAP.
I’m using it for studying Advanced Internet Technologies.
As sources, I used W3C official specification and w3schools.
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, DyCaPo will implement full Dynamic Carpooling functionalities as well as static approaches.
More information and download on the official page.
Here are the release notes and the changes since 0.0.1:
RELEASE NOTES *************** 2010-01-10 Daniel GraziotinDycapo 0.0.2 is just for _showing_out_some_functionalities_ of the system and testing the underlying technologies. Dycapo 0.0.2 incorporates and shows: * OpenTrip Core adoption and OpenTrip Dynamic data structures proposal (in Django Model format) * Use of XML-RPC with Django (rpc4django over HTTP and HTTPS) * (Sort of) integration of Dycapo models with Django and rpc4django * Authentication * Insertion of a trip by a driver * Start of a trip by a driver * Search of a trip by a rider * Send a ride request to a driver * Let the driver accept the ride request No one exported XML-RPC function will surely be included in the final API! No one exported XML-RPC function is either optimized or completely working! Code is (somewhat) documented. Expect a completely better work for 0.1.0 
CHANGES SINCE 0.0.1 *************** Some refactoring to make the code cleaner. Lots of bugs fixed. Test suite rewritten and (finally) fully working. models.py: - added utility methods (i.e. __unicode__ and to_xmlrpc) - use of OpenTrip id proposal instead of Django id - addition of fields to Participation model, regarding a ride request and a request accepted trip.py: this module has been splitted in four files: - driver.py - holds all the XML-RPC methods that a Driver needs. - rider.py - holds all the XML-RPC methods that a Rider needs. - commin.py - will hold all the XML-RPC methods shared by Rider and Driver - utils.py - holds some utility functions. driver.py (formerly trip.py): - added check_ride_requests(trip) - checks for ride requests - added accept_ride_request(trip, person) - for accepting a Rider rider.py (formerly trip.py): - added request_ride(trip) - sends a ride request to a trip tests/: - Cleaner code and better organization - Added test_all_simple.py - creates a Driver and a Rider with the same destination as target - test_all.py - creates 3 drivers and 5 riders with random locations as target
It’s a pleasure for me to announce Dycapo-0.0.1, the very first release of the project.
Dycapo-0.0.1 is part of the pre-alpha-dontuse releases, to only illustrate some functionalities.
Here are the release notes:
2009-12-26 Daniel Graziotin <daniel DOT graziotin AT gmail DOT com>
Dycapo 0.0.1 is just for showing out some functionalities of the system and
testing the underlying technologies.
Dycapo 0.0.1 incorporates and shows:
- OpenTrip Core adoption and OpenTrip Dynamic data structures proposal (in Django Model format)
- Use of XML-RPC with Django (rpc4django over HTTP and HTTPS)
- (Sort of) integration of Dycapo models with Django and rpc4django
- Authentication
- Insertion of a trip by a driver
- Start of a trip by a driver
- Search of a trip by a rider
- Accepting a ride
No one exported XML-RPC function will surely be included in the final API!
No one exported XML-RPC function is either optimized or completely working!Code is (somewhat) documented. Expect a completely better work for 0.1.0
You can read much more about Dycapo and download it at Dycapo official project page. Project page also hosts installation instructions and configuration steps.
The research behind Dycapo (Dynamic Carpooling system) is illustrated here.
I love to be back to Slackware, my very first distribution. However, there are a couple of things that I’m missing from the other more comfortable distributions. From among them, I totally miss Network Manager.
I saw many people asking in forums on how to install Network Manager in Slackware 13.0. There is Wicd, already present in Slackware “repositories”. Every Slackware maniac will tell you that it does the same job of Network Manager, but I don’t agree. It does not always work and is more complicated to be configured than NM.
Anyway, I’m going to explain to Slackware newbies the dirty way to have a fully working Network Manager on Slackware 13.0. This method is totally against Slackware philosophy and will also replace some important libraries of the system! Anyway, the packages being replaced are prepared from the guys behind GNOME SlackBuild, a project to bring Gnome in every Slackware release.
You have two way to have Network Manager in your Slackware: either install the entire Gnome from them (or any other similar project) or use slapt-get against their repositories and just install Network-Manager. Here are the instructions. All the following actions must be performed as root user:
slapt-get –update
slapt-get –dist-upgrade
SOURCE=http://mirror.switch.ch/ftp/mirror/gsb/gsb-current/
slapt-get –update
slapt-get –add-keys
slapt-get –install –reinstall alsa-lib bluez glib2 gtk+2 libwnck
slapt-get –install NetworkManager network-manager-applet
chmod +x /etc/rc.d/rc.messagebus /etc/rc.d/rc.hald /etc/rc.d/rc.networkmanager
netdev:x:86:root
Add your username after root (bodom_lx is my case)
netdev:x:86:root,bodom_lx
cd ~/.kde/Autostart/
Create a file called nm-applet.sh with the following content:
#!/usr/bin/bash
nm-applet –sm-disable &
Give it execution permission:
chmod +x nm-applet.sh
.
Reboot your system. Everything should work fine now.
To uninstall Network Manager and restore the system as it was before the installation follow these instructions, as root::
removepkg /var/log/packages/*gsb
#SOURCE=http://mirror.switch.ch/ftp/mirror/gsb/gsb-current/
slapt-get –update
slapt-get –reinstall –install glib2 libwnck alsa-lib gtk+2
chmod -x ~/.kde/Autostart/nm-applet.sh
Feel free to comment any suggestion.
Twitter
Recent Comments