After more than a week of work from time to time, the first changes have been committed to the trunk branch.
For now, only basic encoding/decoding implementation capabilities are available. Despite no documentation and few comments are in the code, diameter_client.erl and diameter_server.erl examples are supplied to show how to implement basic clients/servers that exchange their capabilities and later just send watchdog messages to each other. Both of them have been tried to work with each other and with external tools to check that implementation is correct for now.
To test the examples, just run the following statements in your erlang shell:
diameter:start().
PidC = diameter_client:start().
PidS = diameter_server:start().
There are lots of pending things yet, but for a first commit it's fine.
Friday, February 29, 2008
Wednesday, February 20, 2008
Renewed energies
This is the first post for the diameterl blog. Diameterl is a project whose aim is to write a diameter protocol stack as specified in RFC3588 in erlang language. The project is currently hosted in launchpad and its URL is: https://launchpad.net/diameterl.
This project that has been in my mind for a long time, but I have never had time to spend on it because of various reasons. However, today it has been a different day, I have received an e-mail asking for information about the project. I have uploaded no code at all, but I have received a request for information. Isn't that encouraging? I think so and, consequently, now I'm looking with renewed energies to the project.
Let's see if with all this new energy some code is committed to the trunk branch. I hope to explain this in the next post. See you!
This project that has been in my mind for a long time, but I have never had time to spend on it because of various reasons. However, today it has been a different day, I have received an e-mail asking for information about the project. I have uploaded no code at all, but I have received a request for information. Isn't that encouraging? I think so and, consequently, now I'm looking with renewed energies to the project.
Let's see if with all this new energy some code is committed to the trunk branch. I hope to explain this in the next post. See you!
Subscribe to:
Posts (Atom)