Timeline for Class design for writing multiple versions of multiple files
Current License: CC BY-SA 3.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 29, 2015 at 15:59 | history | bounty ended | CommunityBot | ||
| S Oct 29, 2015 at 15:59 | history | notice removed | CommunityBot | ||
| Oct 24, 2015 at 20:28 | history | edited | vjain27 | CC BY-SA 3.0 | added 3 characters in body |
| Oct 22, 2015 at 13:33 | history | edited | vjain27 | CC BY-SA 3.0 | added 259 characters in body |
| Oct 22, 2015 at 13:24 | history | edited | vjain27 | CC BY-SA 3.0 | added 259 characters in body |
| Oct 22, 2015 at 12:36 | answer | added | back2dos | timeline score: 5 | |
| Oct 22, 2015 at 11:56 | answer | added | Ewan | timeline score: 0 | |
| Oct 22, 2015 at 5:56 | history | edited | vjain27 | CC BY-SA 3.0 | added 450 characters in body |
| Oct 22, 2015 at 2:50 | comment | added | technosaurus | You are using JSON and a web service. There is no reason you can't just add json obects as needed and append versioning info etc... via a GET request to the URI host/file.ext?v=1¶m=value&... or use JSON for passing parameters in a POST. You haven't stated why new files are needed. If you just append new json objects in v2, then v1 can still use the same file and v2 can use default values for any new objects when it needs to read a v1 file. | |
| Oct 21, 2015 at 19:31 | comment | added | Luminous | I'm trying to figure out your architecture and my best advice is remember to separate what's different from what stays the same. Take a look at what changes you're applying to your POJOs and maybe you need to abstract the amount and types of parameters you're passing into your generators. | |
| S Oct 21, 2015 at 14:34 | history | bounty started | vjain27 | ||
| S Oct 21, 2015 at 14:34 | history | notice added | vjain27 | Draw attention | |
| Oct 21, 2015 at 4:37 | history | edited | vjain27 | edited tags | |
| Oct 21, 2015 at 4:26 | history | edited | vjain27 | CC BY-SA 3.0 | edited title |
| Oct 20, 2015 at 16:42 | history | edited | vjain27 | CC BY-SA 3.0 | added 40 characters in body |
| Oct 19, 2015 at 18:06 | history | edited | vjain27 | CC BY-SA 3.0 | added 340 characters in body |
| Oct 19, 2015 at 16:46 | comment | added | TMN | You might want to look into the strategy pattern. | |
| Oct 19, 2015 at 4:51 | comment | added | vjain27 | I have added skeleton code for clarity. Thanks for responding. | |
| Oct 19, 2015 at 4:50 | history | edited | vjain27 | CC BY-SA 3.0 | Added code for clarity |
| Oct 19, 2015 at 4:03 | comment | added | J Trana | I had a bit of difficulty following your current architecture. Could you perhaps show some form of diagram or describe a bit more clearly how your code currently works? I think I understand some aspects of it, but other important parts - like how the generators are parametrized, what parts of versioning are already plumbed in, etc - could perhaps use a bit more clarity. | |
| Oct 19, 2015 at 2:30 | history | edited | user40980 | CC BY-SA 3.0 | Add additional line feed to break up text as indicated by source. |
| Oct 19, 2015 at 2:23 | review | First posts | |||
| Oct 19, 2015 at 13:14 | |||||
| Oct 19, 2015 at 2:22 | history | asked | vjain27 | CC BY-SA 3.0 |