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.
Road to 0.0.1 for Dycapo. Today I succesfully wrote a first xml-rpc method accepting OpenTrip Core objects, that inserts a trip chosen by the driver.
def add_trip(trip, mode, source, destination)
Actually, the driver is automatically retrieved by the system, since we are waiting rpc4django 0.1.6 to come out and access User from requests. Moreover, only a source and a destination Locations can be specified.
But it works. It works fine.
The method is located at: server/trip.py
I also wrote a tiny python client to test the remote call, located at: tests.
In a couple of days I should try to publish Dycapo 0.0.1. That’s what I hope 
At the end we decided to adopt OpenTrip. I could propose the Dynamic extension of the protocol, over XML-RPC.
By the way, I opened a GitHub repository to host the source code of Dycapo. At this moment I just implemented and documented the models.
Dycapo project source code is hosted on: http://github.com/BodomLx/dycapo.
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