1,184 reputation
36
bio website
location
age
visits member for 3 years, 2 months
seen yesterday

Mar
17
comment PHP OOP: value property is guaranteed different?
yes, the requests are separated so they won't mix at all. If you want to share between requests you need to store the data in a database / file for example. All running code is never mixed. For the same user the session is also an exception, that is also stored in for example a file and shared between your own requests.
Mar
15
comment How to save many changes to database data?
Is it single user or multiple users active on the same sheet?
Feb
19
comment RESTful basic http atuhentication credentials
search for api tokens. You start with login, then you receive a token from the server you can use. When it's not valid anymore you login again and so on.
Feb
19
comment Consuming a rest API that exposes nested objects
If that's the case an abstract class (or something alike) could solve most. Something like: class Listing { function getData(){} function parseData() {} } etc and then implement the specific classes: CategoryListing implements Listing { var url = '/categories'} SubCategoryListing { var url = /categories/123/ } etc
Feb
19
comment Consuming a rest API that exposes nested objects
and the interface is? For example in simple html/php you simply create one function which loads the top level: /categories. Then loop it with foreach and generate the links. When clicked you load the same script but now the starting point is not /categories but /categories/123 and you show the list again, generate the links and done.
Feb
19
comment Consuming a rest API that exposes nested objects
Do you need them locally or do you just need to give the user an interface to browse the structure?
Feb
17
comment Printing a large number of images from the browser
To do this a PDF generation sounds like a much more logical procedure. Since I expect it's likely you want a pdf anyway I would make it that format instantly. It moves the responsibility of printing all pages to the client. And you can verify the document to ensure all pages are in there.
Feb
9
comment What's the point with HATEOAS on the client-side?
Correct you can make the decision of balance limits as complex as you want and still don't have to make changes to the client. If you take this further with REST parts like content type you can show different views. For example an account looks different from a transaction. Also interesting is code on demand (though not much implemented). That could be used for example for a borrowing estimator. It can give the interface a simple calculator function so the client only needs to implement the inputs for the calculation. It will stay up-to-date from the back-end.
Feb
9
comment REST API - Should API Return Nested JSON Objects?
Yeah, not sure the exact word on this process. HATEOS in general is being used for linking in rest API's but I agree it also has to do with state. Though the idea of implementation will be the same. Here you see a bit more about how it can be used by an example: stormpath.com/blog/linking-and-resource-expansion-rest-api-tips
Feb
9
answered What's the point with HATEOAS on the client-side?
Feb
9
answered REST API - Should API Return Nested JSON Objects?
Feb
6
comment How do you stay productive when dealing with extremely badly written code?
"I was assigned to add logging to a large SharePoint project" does not sound like a goal which is very satisfying to reach. Isn't the goal for example: To let the client make more profit because we can make the software more stable? Or make the users happier because we have more insight so we can help them better? I feel while reading your post that logging isn't the goal and you are pursuing the method instead of the goal. And yes that's dissatisfying. Think about when you start a new project, you have a goal, a visible result. The goal is not to write some controllers but to build the app.
Feb
4
comment What to use instead of IDs in selectors in CSS
Think about it, when you need a third list which contains data of the same class (opening for example) you would have to duplicate you css to specifically style it. Because you can use an ID only once. With classes you could just copy the html and styling will fit. Also semantically makes sense because it's the same sort of data which because of that gets the same class.
Feb
4
comment Best practice for uploading large file, previewing, and editing before saving to database?
Actually when you do not want to store the data on your server but you need to process it on the server it's about the only way to continuously send it around. You might make it a bit more fluent by not using just traditional requests but implement ajax like features but that's about the limit. Other options need a server side storage of the data somewhere. And that generally (outside of memory databases - oops - memory storage) is about the only option. I suspect your requests are not well understood / well grounded in this case. A simple database solution with a cronjob to clean should work.
Feb
3
comment RESTful Api: Send email with links to client URL
Yes sounds very reasonable. It's not unRESTfull to do it in the login procedure but still it sounds like a good choice. Also I think developers like it because it gives more control. You can also send out a validation error when it's in config but it less obvious clearly.
Feb
2
comment RESTful Api: Send email with links to client URL
I was interested in whether you are going to require your clients to do a setup/registration for your API where they enter the desired urls or that you are going to get the info from request itself?
Feb
2
comment RESTful Api: Send email with links to client URL
cool, so what kind of direction are you following? Are you going for setup for the client or use some request headers?
Feb
2
awarded  Yearling
Feb
2
revised RESTful Api: Send email with links to client URL
Based on the new question details explained in more detail about url templates since that seems to be the point which gets understood wrong.
Feb
1
comment Should I keep email addresses as plaintext in database?
You could setup a separate application which stores only email + passwords (+other private data) for example. You could use that to send emails by calling it, for example with a internal rest api: localEmailServer/sendInvite/123 where 123 = user id. You can do the same for login, post to localEmailServer/login which can return true or false. That way your application can get hacked but still they won't have the e-mailaddresses. If you limit the amount of requests to this service it's more protected because you are not vulnerable to things like SQL injections on this part.