Forget the file.

On Sat, May 21, 2011 at 8:00 PM, Luis A. Bastiao Silva
<[email protected]>wrote:

> Hello guys,
>
> Eugene is a student working in USoC 2011. He is now working on HTTP
> protocol
> to UMPA.
>
> Take a look, waiting for feedback.
>
> ---------- Forwarded message ----------
> From: Eugene Melnichenko <[email protected]>
> Date: 2011/5/21
> Subject: HTTP Protocol
> To: João Medeiros <[email protected]>, Luis Kop <[email protected]>
>
>
> Hi guys!
> Sent you my studies for the problem of HTTP protocol.
> The code is still very crude, so that particularly do "not scold" :)
> If you have any questions or advice, please contact me.
> Since the first task is almost ready, I can simultaneously run the
> following.
> Thanks!
>
>
>
> --
> Luís A. Bastião Silva
> Skype: koplabs
> http://www.bastiao.org
>
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Umit-gsoc mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/umit-gsoc
>
>


-- 
Luís A. Bastião Silva
Umit Project Developer
Skype: koplabs
http://www.umitproject.org
http://www.bastiao.org

Attachment: HTTP Protocol.py
Description: Binary data

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Umit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/umit-devel

Reply via email to