hcd

Network Services Kit Introduction

Blog post by AntiRush on Sun, 2009-05-17 03:20

Hello Haiku World, I'm Tom Fairfield and I've been chosen to work on a project for the Code Drive this summer. You'll see me around IRC and elsewhere as fairfieldt or AntiRush. I'm a 4th year computer science major at Xavier University in Cincinnati, Ohio.

I've been interested in operating system development for quite some time and Haiku is a great looking project in that regard.

The project I proposed and was chosen to complete is a Network Services Kit for Haiku.

List of project goals:
o Design an API for the Services kit
o Implement a basic Services Kit that provides this base API that's extendable for any web service
o As a byproduct create various utility classes for HTTP/HTTPS and other web-oriented functions that can be easily re-used.
o Build a Twitter service on top of the base Services Kit
o Write a proof-of-concept application that utilizes the Twitter functions of the Services Kit
o Fully document the base Services Kit so that it is easy for future developers to add their own services. This will be both documenting the API and with a tutorial following the implementation of a protocol. Given time the tutorial will be written in conjunction with another server. Flickr? Facebook?
o Fully document the Twitter Service as well as the application. Again this will be both API documentation and a tutorial following the development of the Twitter application to demonstrate the use of the Services Kit.

The first step is to design and implement the HTTP library. I've been working with Pier Fiorini to design an api for both the HTTP library and the Network Services kit itself. At this point I've begun writing code for the HTTP side of things.

I'll try to frequently update with new blog posts to keep the community involved. Any comments or suggestions are more than welcomed - it can only make my project better!

HCD [bfs]: Status Report #1

Blog post by emitrax on Sun, 2008-06-22 17:33

It's been almost a month already since the very first Haiku Code Drive began!

First of all thanks to all of those who have voted me, I was very surprised about the poll result.

Now some updates about my project.

As you know, my project aims to test the stability of the bfs file system. In order to do so
the idea is to first implement XSI Posix semaphores, and then compile bonnie++ which is a benchmark suite
for file systems. To be honest though, XSI Posix semaphore are not really mandatory, because it would be
faster to just port bonnie++ to Haiku, as it would require very few changes (e.g. those concerned locking).
However though, in the long run, Haiku would benifit more if I implement the semaphores previously mentioned,
as it would also make it more Posix compliant.

The easiest part was the user space one, now I'm working on the kernel side. I also started a thread
about this on the gsoc mailing list so you can follow it by clicking on the link below.
http://www.freelists.org/archives/haiku-gsoc/06-2008/msg00009.html

Although I'm not done with the above though, I've already started running some test without bonnie++
and hitting the first bug. See ticket #2400.

The test is quite simple but very time consuming, especially on my current hardware (by the way,
if someone is willing to try the test with real hardware or a faster maching please contact me).

I first packed the whole haiku source code into a tarball from linux, move it to my usb disk, run
vmware, and try to unpack the almost 500MB tarball (1.5 GB unpacked) from Haiku.
Yeah... "Good luck with that! :)"

The result, which at first seemed to me as a bfs bug, turned out to be a vfs one, although we are still discussing about it in the gsoc mailing list. See the link below for more details.
http://www.freelists.org/archives/haiku-gsoc/06-2008/msg00021.html

Despite the fact it has been confirmed not to be a bfs bug, as you can read from the mailing list, I'm still trying to fix it, while also finishing xsi sempahore implementation.

That's all for now.

Syndicate content