D - Phobos cross-platform networking layer?
- Brian Bober (3/3) Jun 04 2002 I noticed that Phobos didn't have a high-level networking layer for
- Jonathan Andrew (10/16) Jun 05 2002 Aside from using C socket functions, D could use a nice native set of
- Pavel Minayev (5/10) Jun 05 2002 You mean, Berkeley sockets?
- Jonathan Andrew (6/24) Jun 05 2002
- Pavel Minayev (7/9) Jun 05 2002 of
- Sean L. Palmer (4/4) Jun 05 2002 I'm translating DirectX 8 to D and ran into some #pragma pack to control
- Pavel Minayev (19/22) Jun 05 2002 if
- Sean L. Palmer (7/29) Jun 05 2002 Does it work on module-scope globals too?
- Pavel Minayev (4/8) Jun 05 2002 Not sure. I think so (since it's an attribute like all others), but
- Jonathan Andrew (5/10) Jun 05 2002 Getting it to work with Walter's windows.d wouldn't make socket.d (or
- Pavel Minayev (10/14) Jun 05 2002 socket.d is just a wrapper over a couple of socket functions. winsock.d
- Jonathan Andrew (9/19) Jun 05 2002 A wrapper function would be nice, as people could use whatever name they
- Pavel Minayev (5/10) Jun 05 2002 socket.d does exactly this.
- Jonathan Andrew (13/32) Jun 05 2002 Ah, I hadn't yet had a chance to look at it, and assumed from your
I noticed that Phobos didn't have a high-level networking layer for cross-platform access to networking routines. In this connectivity-driven world, I feel that is something that might come in handy. What do you think?
Jun 04 2002
Brian Bober wrote:I noticed that Phobos didn't have a high-level networking layer for cross-platform access to networking routines. In this connectivity-driven world, I feel that is something that might come in handy. What do you think?Aside from using C socket functions, D could use a nice native set of net functions, or at least wrappers for the C functions. I've given some thought to starting on these myself, but I am not very skilled at writing network code (or much code at all! ;) ), and I'm not sure what people are looking for in a net API, i.e. object-oriented, wrapper-functions, etc... I'm sure somebody much more skilled than me has given some thought to this or begun work on it. My current projects are all net based, and I would love to port them to D. -Jon
Jun 05 2002
"Jonathan Andrew" <jon ece.arizona.edu> wrote in message news:3CFDBB0A.2020702 ece.arizona.edu...Aside from using C socket functions, D could use a nice native set ofYou mean, Berkeley sockets?net functions, or at least wrappers for the C functions. I've given some thought to starting on these myself, but I am not very skilled at writing network code (or much code at all! ;) ), and I'm not sure what people are looking for in a net API, i.e. object-oriented,See http://int19h.tamb.ru, the sockets module. I don't say it's perfect, but at least it works. =)
Jun 05 2002
Pavel Minayev wrote:"Jonathan Andrew" <jon ece.arizona.edu> wrote in message news:3CFDBB0A.2020702 ece.arizona.edu...Yup.Aside from using C socket functions, D could use a nice native set ofYou mean, Berkeley sockets?Ah, well you are already ahead of me! I'll take a look at it! Any chance of this being a part of phobos in the future? -Jonnet functions, or at least wrappers for the C functions. I've given some thought to starting on these myself, but I am not very skilled at writing network code (or much code at all! ;) ), and I'm not sure what people are looking for in a net API, i.e. object-oriented,See http://int19h.tamb.ru, the sockets module. I don't say it's perfect, but at least it works. =)
Jun 05 2002
"Jonathan Andrew" <jon ece.arizona.edu> wrote in message news:3CFDC172.5050003 ece.arizona.edu...Ah, well you are already ahead of me! I'll take a look at it! Any chanceofthis being a part of phobos in the future?You better ask Walter... =) anyhow, this thing is currently tied to my windows.d, but, as soon as I have some more free time (in a week or two), I'll fix it to work with Walter's windows.d. Then, it could be a candidate for inclusion into Phobos.
Jun 05 2002
I'm translating DirectX 8 to D and ran into some #pragma pack to control struct member alignment. Is there any equivalent for this in DMD? (even if it's not "standard" D) Sean
Jun 05 2002
"Sean L. Palmer" <seanpalmer earthlink.net> wrote in message news:adlgtt$15fq$1 digitaldaemon.com...I'm translating DirectX 8 to D and ran into some #pragma pack to control struct member alignment. Is there any equivalent for this in DMD? (evenifit's not "standard" D)Standartized D equivalent is the align() attribute. It can be applied both to entire structures, and to their parts: align(1) struct foo // align entire struct on bytes boundaries { byte a; int b; } struct bar { align(2): // align on word boundaries from now on byte a; int b; align(4): // align on dword boundaries from now on short c; long d; }
Jun 05 2002
Does it work on module-scope globals too?
align(1):
struct foo { byte a,b; }
struct bar { char c,d; }
Sean
"Pavel Minayev" <evilone omen.ru> wrote in message
news:adli7a$16m1$1 digitaldaemon.com...
"Sean L. Palmer" <seanpalmer earthlink.net> wrote in message
news:adlgtt$15fq$1 digitaldaemon.com...
I'm translating DirectX 8 to D and ran into some #pragma pack to control
struct member alignment. Is there any equivalent for this in DMD? (even
if
it's not "standard" D)
Standartized D equivalent is the align() attribute. It can be applied both
to entire structures, and to their parts:
align(1) struct foo // align entire struct on bytes boundaries
{
byte a;
int b;
}
struct bar
{
align(2): // align on word boundaries from now on
byte a;
int b;
align(4): // align on dword boundaries from now on
short c;
long d;
}
Jun 05 2002
"Pavel Minayev" <evilone omen.ru>
"Sean L. Palmer" <seanpalmer earthlink.net> wrote in message
news:admqpu$2d6i$1 digitaldaemon.com...
Does it work on module-scope globals too?
align(1):
struct foo { byte a,b; }
struct bar { char c,d; }
Not sure. I think so (since it's an attribute like all others), but
it should be tested.
Jun 05 2002
Pavel Minayev wrote:You better ask Walter... =) anyhow, this thing is currently tied to my windows.d, but, as soon as I have some more free time (in a week or two), I'll fix it to work with Walter's windows.d. Then, it could be a candidate for inclusion into Phobos.Getting it to work with Walter's windows.d wouldn't make socket.d (or net.d or whatever it would eventually be called) dependent on windows.d, would it? Just thinking of us Linux folks... -Jon
Jun 05 2002
"Jonathan Andrew" <jon ece.arizona.edu> wrote in message news:3CFE7247.7050706 ece.arizona.edu...Getting it to work with Walter's windows.d wouldn't make socket.d (or net.d or whatever it would eventually be called) dependent on windows.d, would it? Just thinking of us Linux folks... -Jonsocket.d is just a wrapper over a couple of socket functions. winsock.d is the one which is tied to windows.d - it is just a straight translation of winsock.h, and there is some Win32-specific stuff there. Also functions are renamed M$-style - closesocket() instead of close() etc - I guess it's better be changed. However, if you leave only the Berkeley structs and functions there, and rename those needed, it should work fine. socket.d also uses names like closesocket()... well, I guess a simple search'n' replace would do fine, or a one-line wrapper function.
Jun 05 2002
Pavel Minayev wrote:socket.d is just a wrapper over a couple of socket functions. winsock.d is the one which is tied to windows.d - it is just a straight translation of winsock.h, and there is some Win32-specific stuff there. Also functions are renamed M$-style - closesocket() instead of close() etc - I guess it's better be changed. However, if you leave only the Berkeley structs and functions there, and rename those needed, it should work fine. socket.d also uses names like closesocket()... well, I guess a simple search'n' replace would do fine, or a one-line wrapper function.A wrapper function would be nice, as people could use whatever name they are most familiar with. How difficult do you think it would be to package up those functions into a 'socket' or 'connection' class? I'm not much of an OO fan myself, but net programming always seemed like an appropriate place for it. Maybe we could have a seperate class-based interface called net.d that is slightly higher-level than socket.d? Just a thought... -Jon
Jun 05 2002
"Jonathan Andrew" <jon ece.arizona.edu> wrote in message news:3CFE7DA9.7050308 ece.arizona.edu...How difficult do you think it would be to package up those functions into a 'socket' or 'connection' class? I'm not much of an OO fan myself,socket.d does exactly this.but net programming always seemed like an appropriate place for it. Maybe we could have a seperate class-based interface called net.d that is slightly higher-level than socket.d? Just a thought...You mean like a set of clients and servers for various protocols? It could be done...
Jun 05 2002
Pavel Minayev wrote:"Jonathan Andrew" <jon ece.arizona.edu> wrote in message news:3CFE7DA9.7050308 ece.arizona.edu...Ah, I hadn't yet had a chance to look at it, and assumed from your earlier comments that it was just wrappers to make it easier to call the socket function from a D program, instead of putting everything in nice classes. I'm glad you did it the way you did though, I like it. Now if I can just get some time to play with it!How difficult do you think it would be to package up those functions into a 'socket' or 'connection' class? I'm not much of an OO fan myself,socket.d does exactly this.Well, to be honest I was just thinking of what you have already done with socket.d, but a set of classes for different protocols would be very cool, have some base connection class and then have things like FTPConnection, HTTPConnection, etc... all derived from that class. I don't think it would belong in Phobos though. -Jonbut net programming always seemed like an appropriate place for it. Maybe we could have a seperate class-based interface called net.d that is slightly higher-level than socket.d? Just a thought...You mean like a set of clients and servers for various protocols? It could be done...
Jun 05 2002