|
|
| Author |
Message |
< Yaws mailing list ~ POST and {page, Page} result type |
| Guest |
 Posted: Thu Jan 25, 2007 12:26 am |
 |
|
|
Guest
|
Hi All,
When landing page receiving POST data returns {page, Page}, next page is
never displayed because yaws_server tries to fetch POST data from client
again. Could this behavior be fixed in some way? For example POST data
gathered could be saved and returned by yaws_server:call_method(), or
something like {page, Page, BinPostData} could be used for passing
fetched POST data (may be even for modifying it).
Thanks.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Jan 25, 2007 4:35 pm |
|
|
|
Guest
|
Hi,
Looking at the old posts I found that the problem with POST + {page,
Page} is well known one, and author is not certain about why we have to
use this combination at all.
I could try to explain why I tried to use it.
An year ago I had some experience with apache struts. The positive
experience. Struts platform is perfect for separation into model and
presentation.
I'm trying to use similar approach with erlang/yaws.
The central point is to have single web-controller which receives all
http requests (including POSTs). Than requests are mapped to {Module,
Function, Arguments} tuples for further processing.
Presentation layer could be implemented as "fast redirect" to *.yaws
using {page, Page} or just call to some function generating ehtml.
That's it.
Thanks.
Dmitriy Kargapolov wrote:
> Hi All,
> When landing page receiving POST data returns {page, Page}, next page is
> never displayed because yaws_server tries to fetch POST data from client
> again. Could this behavior be fixed in some way? For example POST data
> gathered could be saved and returned by yaws_server:call_method(), or
> something like {page, Page, BinPostData} could be used for passing
> fetched POST data (may be even for modifying it).
> Thanks.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Erlyaws-list mailing list
> Erlyaws-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/erlyaws-list
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Erlyaws-list mailing list
Erlyaws-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlyaws-list
Post recived from mailinglist |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
