Timeline for How to capture transport package?
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 15, 2016 at 14:20 | answer | added | Hiren Kaku | timeline score: 0 | |
Sep 14, 2016 at 15:56 | answer | added | Rob Eades | timeline score: 0 | |
Apr 17, 2014 at 5:32 | comment | added | Alvin Reyes | Capturing transport package details might be useful for things like performance monitoring and testing, though Tridion includes logs and a publishing queue for this. The use case matters because it'll help identify the supported approach for what you're trying to do. Any problems won't be found with what you build now, but if/when the transport package format, approach, or conventions change. | |
Apr 16, 2014 at 12:12 | history | tweeted | twitter.com/#!/StackTridion/status/456404697364979712 | ||
Apr 16, 2014 at 11:00 | comment | added | Dominic Cronin | If you can share just a little more of your thinking, people might be able to help. Are you certain that capturing the package on the publisher is actually necessary? | |
Apr 16, 2014 at 10:26 | answer | added | David Forster | timeline score: 2 | |
Apr 16, 2014 at 10:21 | answer | added | Bart Koopman | timeline score: 2 | |
Apr 16, 2014 at 10:10 | comment | added | user899 | I need to capture information about every publish transaction made. | |
Apr 16, 2014 at 10:06 | comment | added | Dominic Cronin | Why are you trying to do this? | |
Apr 16, 2014 at 10:02 | history | edited | user899 | CC BY-SA 3.0 |
added 115 characters in body
|
Apr 16, 2014 at 9:55 | answer | added | Nuno Linhares♦ | timeline score: 5 | |
Apr 16, 2014 at 9:47 | history | asked | user899 | CC BY-SA 3.0 |