Hi All,
I'm trying to simplify my RIFE application right now by using
PathInfo Mappings:
http://rifers.org/wiki/display/RIFE/Pathinfo+mapping+for+element+inputs
The idea would be to have one single Element per
displayable/modifiable application object and then use REST-ful urls
to tell that Element what it needed to get the job done. For example,
if I had a User object that I wanted to manage, I might expect URLs
like these:
# Standard appraoch HOST/element/action...
HOST/users/view/1 (Would display User information for the User with an id of 1)
HOST/users/add (Would POST the form parameters to create a User object.)
HOST/users/delete/1 (Would delete the User with an id of 1)
.....
Based on the URL linked to above, the PathInfo Mappings are very
simple when you have a finite set of inputs but when you have variable
inputs, which I would have above, things tend to go toward the
undocumented part of RIFE. Now...I know I could easily add the id to
the add url above but that id is not known at form submission time so
that really isn't a possibility. Any insight as to how I could
accomplish this would be great.
Take care,
Jeremy
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"rife-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rife-users?hl=en
-~----------~----~----~----~------~----~------~--~---
