hazaar/hazaar-warlock
1
0
Fork 0
Code Issues Pull requests 2 Projects Releases 4 Packages Wiki Activity Actions

Investigate using named pipes for communication #27

New issue
Closed
opened 2018-02-14 06:03:18 +00:00 by jamie · 10 comments
jamie commented 2018-02-14 06:03:18 +00:00 (Migrated from git.hazaar.io)
Copy link

Using a named pipe could make it more simple to communicate between an app frontend and a running warlock backend.

See: https://stackoverflow.com/questions/17954307/named-pipe-in-php-on-windows-mac-linux

Using a named pipe could make it more simple to communicate between an app frontend and a running warlock backend. See: https://stackoverflow.com/questions/17954307/named-pipe-in-php-on-windows-mac-linux
jamie commented 2018-02-25 23:38:25 +00:00 (Migrated from git.hazaar.io)
Copy link

closed

closed
jamie commented 2018-02-25 23:38:40 +00:00 (Migrated from git.hazaar.io)
Copy link

reopened

reopened
jamie commented 2018-07-12 01:21:39 +00:00 (Migrated from git.hazaar.io)
Copy link

refs #24

refs #24
jamie commented 2018-07-12 01:25:45 +00:00 (Migrated from git.hazaar.io)
Copy link

added ~136 label

added ~136 label
jamie commented 2018-07-12 01:25:56 +00:00 (Migrated from git.hazaar.io)
Copy link

added ~163 label

added ~163 label
jamie commented 2018-07-12 23:34:44 +00:00 (Migrated from git.hazaar.io)
Copy link

created branch 27-investigate-using-named-pipes-for-communication

created branch [`27-investigate-using-named-pipes-for-communication`](https://git.hazaarlabs.com/hazaar/hazaar-warlock/compare/master...27-investigate-using-named-pipes-for-communication)
jamie commented 2018-07-12 23:34:46 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in merge request !9

mentioned in merge request !9
jamie commented 2018-07-14 03:43:02 +00:00 (Migrated from git.hazaar.io)
Copy link

Named pipes are not an option because there is no way to create them from PHP.

Named pipes are not an option because there is no way to create them from PHP.
jamie commented 2018-07-15 11:24:47 +00:00 (Migrated from git.hazaar.io)
Copy link

mentioned in commit 7a7d1b8324

mentioned in commit 7a7d1b8324bce8563bb65ab5317c84a4a71437a1
jamie commented 2018-07-15 11:24:47 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via merge request !9

closed via merge request !9
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
3.0-develop
58-restful-triggers
2.2-stable
2-warlock-to-warlock-communication
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.5
release-2.1.4
release-2.1.3
release-2.1.2
release-2.1.1
release-2.1.0
release-2.0.2
release-2.0.1
release-2.0.0
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
release-0.4.0
release-0.3.0
release-0.2.0
release-0.1.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-warlock#27
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?