Re: NEW: www/websocketd

2015-03-30 Thread Kent R. Spillner
On Thu, Mar 26, 2015 at 02:06:24PM -0500, Kent R. Spillner wrote:
 On Wed, Mar 25, 2015 at 09:44:29AM -0500, Kent R. Spillner wrote:
  Anyone else care to weigh in?  Or anyone want to give me an ok import into
  net?
 
 I assume silence means everyone either agrees or doesn't care enough.  :)
 Attached is a new version with CATEGORIES switched to net www, and I
 tweaked BUILD_DEPENDS for go-websocket's new category, too.  Ok?

Ping.


net_websocketd.tar.gz
Description: application/tar-gz


Re: NEW: www/websocketd

2015-03-26 Thread Kent R. Spillner
On Wed, Mar 25, 2015 at 09:44:29AM -0500, Kent R. Spillner wrote:
 Anyone else care to weigh in?  Or anyone want to give me an ok import into
 net?

I assume silence means everyone either agrees or doesn't care enough.  :)
Attached is a new version with CATEGORIES switched to net www, and I
tweaked BUILD_DEPENDS for go-websocket's new category, too.  Ok?


net_websocketd.tar.gz
Description: application/tar-gz


Re: NEW: www/websocketd

2015-03-25 Thread Kent R. Spillner
On Tue, Mar 24, 2015 at 10:40:22PM +, Stuart Henderson wrote:
 common style is to split BUILD_DEPENDS onto multiple lines, e.g.
 
 -BUILD_DEPENDS =  lang/go www/go-websocket
 +BUILD_DEPENDS =lang/go \
 + www/go-websocket

Done.

 I'm wondering about CATEGORIES though. net seems like maybe it's more
 appropriate than www? (actually...perhaps net is a better place for
 go-websocket too, perhaps with www as a secondary category?...)

Yeah, that makes sense.  I don't have a strong preference which category
is the main one, although www is slightly less crowded and websockets are
fairly web-centric.  But skimming some of the other ports already in www
I don't see many that are similar to these so perhaps net is a more natural
choice for both.

Anyone else care to weigh in?  Or anyone want to give me an ok import into
net?



Re: NEW: www/websocketd

2015-03-24 Thread Stuart Henderson
On 2015/03/24 14:39, Kent R. Spillner wrote:
 With attachment this time.
 
 On Tue, Mar 24, 2015 at 02:35:53PM -0500, Kent R. Spillner wrote:
  Attached is an updated version based on feedback from czarkoff@:
  
  - Reword DESCR
  - Prefer ${...} over $(...)
  
  Ok?
  
  On Mon, Mar 23, 2015 at 11:57:54AM -0500, Kent R. Spillner wrote:
   Ping.
   
   On Wed, Mar 18, 2015 at 12:27:06PM -0500, Kent R. Spillner wrote:
Attached is a new port for websocketd, which lets you access any command
line tool via a websocket.  It depends on the go-websocket port sent
previously.

$ cat pkg/DESCR
websocketd is a small command-line tool that will wrap an existing
command-line interface program, and allow it to be accessed via a
WebSocket.

WebSocket-capable applications can now be built very easily. As long as
you can write an executable program that reads `STDIN` and writes to
`STDOUT`, you can build a WebSocket server. Do it in Python, Ruby, Perl,
Bash, .NET, C, Go, PHP, Java, Clojure, Scala, Groovy, Expect, Awk,
VBScript, Haskell, Lua, R, whatever! No networking libraries necessary.
  
  

common style is to split BUILD_DEPENDS onto multiple lines, e.g.

-BUILD_DEPENDS =lang/go www/go-websocket
+BUILD_DEPENDS =lang/go \
+   www/go-websocket

I'm wondering about CATEGORIES though. net seems like maybe it's more
appropriate than www? (actually...perhaps net is a better place for
go-websocket too, perhaps with www as a secondary category?...)



Re: NEW: www/websocketd

2015-03-24 Thread Kent R. Spillner
With attachment this time.

On Tue, Mar 24, 2015 at 02:35:53PM -0500, Kent R. Spillner wrote:
 Attached is an updated version based on feedback from czarkoff@:
 
 - Reword DESCR
 - Prefer ${...} over $(...)
 
 Ok?
 
 On Mon, Mar 23, 2015 at 11:57:54AM -0500, Kent R. Spillner wrote:
  Ping.
  
  On Wed, Mar 18, 2015 at 12:27:06PM -0500, Kent R. Spillner wrote:
   Attached is a new port for websocketd, which lets you access any command
   line tool via a websocket.  It depends on the go-websocket port sent
   previously.
   
   $ cat pkg/DESCR
   websocketd is a small command-line tool that will wrap an existing
   command-line interface program, and allow it to be accessed via a
   WebSocket.
   
   WebSocket-capable applications can now be built very easily. As long as
   you can write an executable program that reads `STDIN` and writes to
   `STDOUT`, you can build a WebSocket server. Do it in Python, Ruby, Perl,
   Bash, .NET, C, Go, PHP, Java, Clojure, Scala, Groovy, Expect, Awk,
   VBScript, Haskell, Lua, R, whatever! No networking libraries necessary.
 
 


www_websocketd.tar.gz
Description: application/tar-gz


Re: NEW: www/websocketd

2015-03-24 Thread Kent R. Spillner
Attached is an updated version based on feedback from czarkoff@:

- Reword DESCR
- Prefer ${...} over $(...)

Ok?

On Mon, Mar 23, 2015 at 11:57:54AM -0500, Kent R. Spillner wrote:
 Ping.
 
 On Wed, Mar 18, 2015 at 12:27:06PM -0500, Kent R. Spillner wrote:
  Attached is a new port for websocketd, which lets you access any command
  line tool via a websocket.  It depends on the go-websocket port sent
  previously.
  
  $ cat pkg/DESCR
  websocketd is a small command-line tool that will wrap an existing
  command-line interface program, and allow it to be accessed via a
  WebSocket.
  
  WebSocket-capable applications can now be built very easily. As long as
  you can write an executable program that reads `STDIN` and writes to
  `STDOUT`, you can build a WebSocket server. Do it in Python, Ruby, Perl,
  Bash, .NET, C, Go, PHP, Java, Clojure, Scala, Groovy, Expect, Awk,
  VBScript, Haskell, Lua, R, whatever! No networking libraries necessary.




Re: NEW: www/websocketd

2015-03-23 Thread Kent R. Spillner
Ping.

On Wed, Mar 18, 2015 at 12:27:06PM -0500, Kent R. Spillner wrote:
 Attached is a new port for websocketd, which lets you access any command
 line tool via a websocket.  It depends on the go-websocket port sent
 previously.
 
 $ cat pkg/DESCR
 websocketd is a small command-line tool that will wrap an existing
 command-line interface program, and allow it to be accessed via a
 WebSocket.
 
 WebSocket-capable applications can now be built very easily. As long as
 you can write an executable program that reads `STDIN` and writes to
 `STDOUT`, you can build a WebSocket server. Do it in Python, Ruby, Perl,
 Bash, .NET, C, Go, PHP, Java, Clojure, Scala, Groovy, Expect, Awk,
 VBScript, Haskell, Lua, R, whatever! No networking libraries necessary.


www_websocketd.tar.gz
Description: application/tar-gz


NEW: www/websocketd

2015-03-18 Thread Kent R. Spillner
Attached is a new port for websocketd, which lets you access any command
line tool via a websocket.  It depends on the go-websocket port sent
previously.

$ cat pkg/DESCR
websocketd is a small command-line tool that will wrap an existing
command-line interface program, and allow it to be accessed via a
WebSocket.

WebSocket-capable applications can now be built very easily. As long as
you can write an executable program that reads `STDIN` and writes to
`STDOUT`, you can build a WebSocket server. Do it in Python, Ruby, Perl,
Bash, .NET, C, Go, PHP, Java, Clojure, Scala, Groovy, Expect, Awk,
VBScript, Haskell, Lua, R, whatever! No networking libraries necessary.


www_websocketd.tar.gz
Description: application/tar-gz