So... the same as !TelnetD ?

I wanna play...

Ah, but that's a port of existing software, not a new piece of software

Now I have to go back to looking for something useful to write that someone else hasn't written yet

Nah

I could write an RSS reader, and call it !ARSS, but I'm sure we already have enough of those on the platform (RSS readers, not arses. Although...)

Instead, I think I'll work on that Other Update, since the DeathDawn editor manual thingy has been ready for about a month now.

Or! A RISC OS frontend for Inform 7!

(Not that the backend is available on RISC OS yet, either.)

Or! A RISC OS frontend for Inform 7!

(Not that the backend is available on RISC OS yet, either.)

That looks very nice!

Or! A RISC OS frontend for Inform 7!

(Not that the backend is available on RISC OS yet, either.)

Now I have to go back to looking for something useful to write that someone else hasn't written yet

Cheers,
Rich.

Now I have to go back to looking for something useful to write that someone else hasn't written yet

How about that 32bit neutral networking module I keep banging on about, which would enable other people to do use it to write their own RSS feeders etc.?

Justin Fletcher's one enabled me to write a link checker that worked for web, ftp, news and email links in web (and wml!) pages, just by telneting in to various ports and seeing what came back. But he removed the module from his site and it never (officially) got upgraded. So LinkCheck is also dead.

Now I have to go back to looking for something useful to write that someone else hasn't written yet

How about that 32bit neutral networking module I keep banging on about, which would enable other people to do use it to write their own RSS feeders etc.?

Now I have to go back to looking for something useful to write that someone else hasn't written yet

How about that 32bit neutral networking module I keep banging on about, which would enable other people to do use it to write their own RSS feeders etc.?

Is libcurl

a). 32bit neutral
b). any good for this?

I've been planning to investigate using this to write a RISC OS Audioscrobbler plugin for yonks, but it never seems to bubble to the top of the todo list.

Cheers,
Rich.

Now I have to go back to looking for something useful to write that someone else hasn't written yet

How about that 32bit neutral networking module I keep banging on about, which would enable other people to do use it to write their own RSS feeders etc.?

Could do, I guess. Although my Iyonix hasn't arrived yet so I have no way of checking if it's 32bit compatible.

What kind of stuff did you need it to do?

What would the SWI interface be like? etc.

And (IIRC you wanted to use it primarily from BASIC) why can't you just write a BASIC library that provides a friendly interface to the Socket SWIs?

Cheers,
Rich.

But then, you might only end up with me using it, and not others.

I want control over line endings, because IIS is a bastard over those. I then want to wait for output - probably line-by-line so I can get the first line (e.g. HTTP response headers), the full headers or the whole thing.

Or! A RISC OS frontend for Inform 7!

(Not that the backend is available on RISC OS yet, either.)

That looks very nice!

I want control over line endings, because IIS is a bastard over those. I then want to wait for output - probably line-by-line so I can get the first line (e.g. HTTP response headers), the full headers or the whole thing.

So something like:

SYS "SocketSWIThingy_SendLine",socket,str$,line_end_type
SYS "SocketSWIThingy_ReadLine",socket,line_end_type,buffer,buffer_length TO $str (Syntax is probably wrong on that one)
SYS "SocketSWIThingy_SendData",socket,buffer,length
SYS "SocketSWIThingy_ReadData",socket,buffer,length TO bytes_read

So that you can read/write binary data and read/write lines? line_end_type would allow you to choose between CR, LF, CR-LF, and LF-CR. Unless you have some other line ending types you can think of

Cheers,
Rich.

a BASIC library that provides a friendly interface to the Socket SWIs ... But then, you might only end up with me using it, and not others.

In fact, such a module would be very useful, so it wouldn't just be you that uses it - I would as well

Cheers,
Rich.

Presumably you'd also need:
SYS "SocketSWIThingy_Connect",server$,port[,proto] TO socket,result
(where result is success or fail in some way; perhaps success, timed out, server not found?)

SYS "SocketSWIThingy_SetTimeout",timeout (in seconds - or would this be in the Connect SWI, rather than global?)

Oh, and it needs to be fairly multi-tasking capable - if I can put a poll loop in there, so people aren't waiting around for data to return (esp. if the fetch times out), then that'd be great.

a BASIC library that provides a friendly interface to the Socket SWIs ... But then, you might only end up with me using it, and not others.

In fact, such a module would be very useful, so it wouldn't just be you that uses it - I would as well

Presumably you'd prefer a module to a BASIC library though? I'd much rather have the module, which is way beyond my own programming ability to create, but allows everyone to use it, than a handy BASIC library.